Category Archives: Bench

Facilities and Administration SAS IT Share move

FYI, we’re moving the F&A SAS IT share from ISCS-Data to a new NetApp share tonight.  The move should be fairly transparent to the customers as Ben has an update GPO that will properly map their drives.  Please note the new share location is <\\fa.sig.oregonstate.edu\fa>

While this move only affects a few people we’ll eventually be moving all of F&A’s data to the new share.

c

From: Sinnett, Chris
Sent: Thursday, February 04, 2016 2:55 PM
To: Henriques, Alejandro <Hondo.Henriques@oregonstate.edu>; Roberts, Andy <Andy.Roberts@oregonstate.edu>; Winklepleck, Ryan <Ryan.Winklepleck@oregonstate.edu>; Norred, Martin Ray <martin.norred@oregonstate.edu>; Sellers, Kevin <Kevin.Sellers@oregonstate.edu>; Jordan, Nicholas <Nicholas.Jordan@oregonstate.edu>
Cc: Community Network <CN.Help@oregonstate.edu>
Subject: IMPORTANT: SAS IT Share move tonight!
Importance: High

SAS IT customers,

Please read this e-mail in its entirety.

This evening the Community Network will move your shared data from the ISCS-Data server to a new dedicated F&A share (\\fa.sig.oregonstate.edu\fa)

Who:                This will affect everyone in SAS IT

What:               The Community Network will transfer your network data to new storage

When:              Thursday, February 4th, after 5:00 PM

What you need to do:  Please save your work, close your files, and log out of your computer before 5:00 PM this evening.

When you log in tomorrow your computer will reconnect to the new FA share.  Shortcuts, links, or recently used documents in your applications will be broken when you attempt to use them after the move.  Please use the File -> Open menu to locate your files in their new location.  Once you’ve opened the file, the new entry in recently used documents will be functional again.

Please contact Community Network at 7-8787 if you feel that any files are missing or if you need assistance.

Thank you for your patience while we transfer your files the new storage solution.

Your Community Network Support Team

Community Network

IS Client Services

Oregon State University

(541) 737-8787

http://oregonstate.edu/is/client-services/

Casper Outage – January 27th, 2016 5-6pm

From: Dudzik, James
All,

I will be running the upgrade from Casper 9.81 to 9.82 tonight at 5:00 PM. This will cause an outage when the Tomcat service is stopped, the database is backed up, and then the server is rebooted at the end of the upgrade process. I expect this will be about a twenty minute outage, and I will send a note out at the end of the process when everything is back up and running.

Please let me know if you have any questions or concerns.

Thanks!

James Dudzik

iComputing Management Specialist

IS Client Services

541-737-8787, Opt. 2

CN.Help@oregonstate.edu

File restores – Research office

CN crew

Update – 1/22/2016 – 9am

21 files have long file names and SSG/Infrastructure is working on ways to get those fully recovered.

Research files have been recovered.

Snapshot date: Tuesday January 19th at 12pm.

If they are missing files, when you do the recover, just bring back individual files.

The restore window for INTO files is January 18th and earlier, or January 21st 7pm and later.

Impacted files: docx, .doc, .xls, .xlsx, .pdf, etc.
.txt file can be pulled from anywhere
Recovery process
In all cases, recover the file somewhere else and work with customer to verify its the file they need.

Files restored – INTO’s shared drive

CN crew

Update – 1/22/2016 – 9am

There are over 3,000 files in the INTO share that did not restore properly due to long file names. Infrastructure is working through those items.

Files for INTO have been restored/recovered, specifically the following folders:

“Student Services” and “Academic Support Team”

Snapshot date: Tuesday January 19th at 12pm.

If they are missing files, when you do the recover, just bring back individual files.

The restore window for INTO files is January 18th and earlier, or January 21st 7pm and later.

Impacted files: docx, .doc, .xls, .xlsx, .pdf, etc.
.txt file can be pulled from anywhere
Recovery process
In all cases, recover the file somewhere else and work with customer to verify its the file they need.
 

ISCS-MDT upgraded to 2013 Update 2

I have successfully upgraded ISCS-MDT to 2013 Update 2 (6.3.8330). Please be aware that this is what’s considered a quality release; there are no new major features.

Work completed:
– VMWare snapshot created for ISCS-MDT.
– MDT 2013 Update 2 applied.
– MDT build and production shares upgraded.
– MDT build and production boot images updated.
– Updated boot images applied to Windows Deployment Services.

Release notes and Information:
http://blogs.technet.com/b/msdeployment/archive/2015/12/22/mdt-2013-update-2-now-available.aspx

Things you may need to complete:
– For folks who log in to ISCS-MDT directly you may need to recreate/re-pin shortcuts to the MDT Workbench.

Additional notes:

The Assessment and Deployment Kit (ADK) for Windows 10 was recently updated by Microsoft. This version is cited to have issues which could impact some MDT deployment scenarios. I will be doing more testing before moving forward with this update.

WINDOWS CLIENTS: TUESDAY UPDATES

The following applications will be updated tonight via Ninite:

Acrobat: 11.0.13 -> 11.0.14 (details)
Shockwave: 12.2.2.172 -> 12.2.3.183 (no details available)
Silverlight: 5.1.41105.0 -> 5.1.41212.0 (details) Security fix

All Windows users can expect to see ~1GB of updates, the majority of which are for Microsoft Office (details).

Note: These updates do require a reboot.

No issues to report.

CN – COHO auto unlock message removed

What?

Tickets that are locked for 2 hours in new or open status unlock and put the message below into tickets that reside in CN queues – Base, Build Bench, Projects, Remote.

From: System Administrator
Subject: Ticket has been automatically unlocked
Text: This ticket was locked for more than two hours
without any progress. Please follow-up on this issue.

That message has been removed.

Tickets will continue to auto unlock and come back into the queues after 2 hours.

When?

Wednesday January 6th, 2016 – 2:20pm

Why?

The message clutters the ticket and doesn’t add value to people using the ticket, queue, etc. This also reduces the amount of COHO e-mail that is sent to people associated with the ticket.

MILNE COMPUTER LAB UPDATES – December 30th

All Dell Windows computers were updated (Citrix PVS image) in Milne on Wednesday, December 30th.

Bug fixes, improvements, and updates:

  • Fixed Adobe After Effects intermittent crash error 0 :: 42.
    • The fix was to update the video drivers.
  • Fixed newly introduced Adobe After Effects error about not having a disk cache configured.
    • I’ve created a folder C:\Temp and have configured the default user profile to point the cache there.
  • Fixed GPU performance error for Adobe Illustrator.
    • I’ve configured the default user profile to disable this feature and stop prompting the user.
  • Removed the Java update application from the run key in the registry. This should stop the update notifications.
  • Applied Windows updates.
  • Applied Ninite updates.
  • Applied Adobe CC updates.

Newly installed applications (by request):

  • TeXnicCenter
  • MiKTeX
  • MPlus
  • Eclipse IDE

Applications removed:

  • Winsent Innocenti

[ CN Change] – CN staff User plus accounts and Admin accounts

 

What

Internal CN staff user plus accounts will go away / be “merged” with the account you use to log into NWS-term4.

When

January 8th 2016

Why

1 less account to use

Reduced confusion

Better for the backend systems to have 1 administrator type account for computer privilege escalation and communication to systems like Active Directory, BitLocker, SCCM, etc.

Impact to you / what to do

Starting today, Tuesday December 29th, 2015 – Log in with your “admin”/NWS-term4 account for anything that needs escalated privileges, either on the computer or a network/server resource.

The format of the username for the “admin” account is first initial of first name, then first 7 of last name.

  • Example – Joe Smith = jsmith

Encounter problems?

If you encounter problems accessing resources with your “admin” account, please e-mail/contact server support (ssg@helpdesk.oregonstate.edu) with the following information.

  1. Date
  2. Time
  3. Resource you are accessing
  4. Specific error message

NEW CORE MIGRATION: BUSINESS AFFAIRS

Yesterday Business Affairs was moved to the new core network.

Cyder/IP change
All workstations and printers…
Moved from: zone.baf (10.198.30.11 – 10.198.30.252)
Moved to: zone.cn_univadmin (10.160.120.150 – 10.160.123.253)

Printer change
Old IP printers were removed from workstations and replaced with new print queues:

Printer address: \\iscs-printq\KAd-100-Back-Ricoh-MP-3351
Printer IP: 10.160.120.225
Printer driver: PCL6 Universal v4.6
Security group: CN_Printers_KAd 100 Back Ricoh MP 3351

Printer address: \\iscs-printq\KAd-100-Front-Ricoh-MP-3351
Printer IP: 10.160.120.226
Printer driver: PCL6 Universal v4.6
Security group: CN_Printers_KAd 100 Front Ricoh MP 3351

Printer address: \\iscs-printq\KAd-100-HP-Color-LaserJet-M451DN
Printer IP: 10.160.120.232
Printer driver: Model-specific PCL6
Security group: CN_Printers_KAd 100 HP Color LaserJet M451DN

Printer address: \\iscs-printq\KAd-100-HP-Color-LaserJet-M452DN
Printer IP: 10.160.120.235
Printer driver: Model-specific PCL6
Security group: CN_Printers_KAd 100 HP Color LaserJet M452DN

Printer address: \\iscs-printq\KAd-100-HP-LaserJet-9050DN
Printer IP: 10.160.120.234
Printer driver: HP Universal Printing PCL 6 (v6.0.0)
Security group: CN_Printers_KAd 100 HP LaserJet 9050DN

Printer address: \\iscs-printq\KAd-100-HP-LaserJet-M401DNE
Printer IP: 10.160.120.229
Printer driver: Model-specific PCL6
Security group: CN_Printers_KAd 100 HP LaserJet M401DNE

Printer address: \\iscs-printq\KAd-100-HP-LaserJet-M602N
Printer IP: 10.160.120.233
Printer driver: HP Universal Printing PCL 6 (v6.0.0)
Security group: CN_Printers_KAd 100 HP LaserJet M602N

Printer address: \\iscs-printq\KAd-100-HP-LaserJet-P2015N
Printer IP: 10.160.120.228
Printer driver: HP Universal Printing PCL 6 (v6.0.0)
Security group: CN_Printers_KAd 100 HP LaserJet P2015N

Printer address: \\iscs-printq\KAd-100-HP-LaserJet-P3015DN
Printer IP: 10.160.120.231
Printer driver: HP Universal Printing PCL 6 (v6.0.0)
Security group: CN_Printers_KAd 100 HP LaserJet P3015DN

Printer address: \\iscs-printq\KAd-100-Ricoh-MP-201
Printer IP: 10.160.120.227
Printer driver: PCL6 Universal v4.6
Security group: CN_Printers_KAd 100 Ricoh MP 201

Printer address: \\iscs-printq\KAd-106-HP-LaserJet-2430TN
Printer IP: 10.160.120.224
Printer driver: HP Universal Printing PCL 6 (v6.0.0)
Security group: CN_Printers_KAd 106 HP LaserJet 2430TN

Printer address: \\iscs-printq\KAd-106-HP-LaserJet-4250TN
Printer IP: 10.160.120.230
Printer driver: HP Universal Printing PCL 6 (v6.0.0)
Security group: CN_Printers_KAd 106 HP LaserJet 4250TN

ONID GPO: TSS – Printer Deployment – Business Affairs
TSS GPO: Printer Deployment – Business Affairs

Resolved Issues

  • Upon arrival, 51 of 76 hosts were able to get online, the remainder have been resolved.
  • Michael Green’s port was documented but didn’t get flipped and was first to get resolved through Telecom.
  • A number of misconfigured ports were addressed with Telecom.
  • 8 printers weren’t online and were resolved by either rebooting, fixing network ports, or reconfiguring printers (switching from BOOTP to DHCP).
  • Various adjustments were made to user permissions on printers.
  • The TSS printer deployment GPO was initially pulled since users had unified accounts but we discovered some general-use and regular users who hadn’t been unified so the GPO was reinstated.
  • The whereabouts of the Ricoh 201 was unknown until after the migration and was reinstated via Group Policy for the folks that use it.
  • Jon Bickler had a hard-coded IP and was set back to DHCP.
  • CN-Lites had to be moved in Cyder. Additionally, the HP 4250 they print to had to be updated on cnlite1 & 2. Finally, cnlite1 & 2 had to be added to the firewall to allow printing.
  • Folks who RDP into ECSI were unable to print to their new print queues. One of the employees identified a workaround.
  • Connectivity to the security cams in the Cashier’s Office broke, Rich Giesige resolved this by updating some firewall rules.

Unresolved Issues

  • Max Schmidt is verifying printing from CN-Lite.
  • More details needs to be gathered about the workaround for ECSI printing.