The process for joining CN Mac computers to the domain has been updated. The domain join through casper now uses an account that we control that lives on the ONID domain. The domain join policy is set up to join all CN Mac computers to onid/delegated/tss/information services/client services/OSU Computer Helpdesk/Computers/CN Mac Computers. After joining a machine to the domain, verify that it is indeed in that location.

The domain bind policy can be found in Casper Self Service.

Remember: Joining macs are still only to be done in extreme circumstances of multiple (4+) users.

As always, if you have any questions feel free to ask away!

-CJ

We’re “complete” with the new core cutover for our customers in Ballard. As part of the building remodel, new core gear was installed in a new switch closet on the third floor, and is set up in parallel with the old core gear (new ports in all the offices, etc). The old core gear is scheduled to be turned off and removed sometime over the winter break. At this point, there are just a couple things left to do:

• There are a couple ports that need to be patched in the switch closet by Telecom
• Folks who have been out of the office with a laptop (or machines we were otherwise unable to get into with the customer there) will need to call in to get printers fixed.

The TD ticket with all of the printer info on the migration is #2291635 – if customers call in needing to have their printers fixed, this should be a quick thing over the phone. If we need to actually move someone to a new core port (e.g. they’re on 128.193.x.y space), that can be a standard field job if the customer isn’t comfortable moving to the new network jack (There are spare patch cables in the new switch closet, 328A)

The following applications have been updated to the latest version in Self Service:

• VLC (2.2.4)
• Google Chrome (54)
• Google Earth (7.1)
• Firefox (ESR 45)

Due to lack of use and out of date software, the following application policies have been retired in Self Service:

• Google Drive
• Skype
• Office 2011

If anyone has any questions, feel free to let me know!

-CJ

Over the Thanksgiving holiday, Enterprise Computing will be upgrading/moving OSU’s administrative Oracle databases (what powers Banner, Data Warehouse, Nolij, and many other services/applications). Notices have already gone out to Outages as well as DCA-All, and a notice will also be going out to users with some level of access to these databases.

What this means for us:
After the database move/upgrade, users will need to use an updated TNSNames.ora file to point to the new location. This file is located in the <Oracle install directory>\Network\Admin folder (typically c:\Oracle\Ora11\Network\Admin). A basic version of this new file (with the standard “OSU” connections) is located at \\software\software\Oracle\11\TNSNAMES\OSU

Starting on Saturday, November 26th, we’ll be pushing the updated version of the file to machines that have the standard TNSNames.ora in the standard location (and thus can be safely overwritten). This covers around 90% of the oracle installs across the fleet.

For users with a nonstandard TNSNames.ora file (or one in a nonstandard location), we cannot safely overwrite the file. These users will be notified of this separately, and may call in for assistance. If all someone accesses is OSU resources, we can assist in replacing the file (rename the old file first). If a user has a customized file, we’ll need to assist them in updating the file via the instructions located in this helpdoc: http://oregonstate.edu/helpdocs/osu-applications/oracle-connections-administrative-databases

The escalation path for issues arising from this change is:

Service Desk -> IT Support Group/DCA (if not a CN customer) -> ACT Support (ACT_Support@lists.oregonstate.edu)

For our Windows 10 clients, we’re making the following changes to how we handle updates. First of all, we’re going to be changing to use Windows 10 CB (Current Branch) for updates and servicing, instead of Windows 10 LTSB (Long Term Servicing Branch). LTSB is generally intended to be used in cases where feature updates are undesirable (e.g. medical equipment, lab equipment, or other specialized + sensitive hardware is attached to the machine), but it also removes many features that customers may want to use (Built in photo viewer, edge browser, Cortana, etc).

Windows 10 updates fall into one of two categories:

• Updates are security updates and fixes to existing components/features.
• Upgrades are additional features/functionality (which may also include security updates).

Both categories are set to be immediately available to Client Services internal machines (once they’re approved in WSUS). Customer machines will receive updates on a one week delay, and will receive upgrades on a one month delay.

One important note here is that because the delays for customer machines are implemented via group policy, moving a machine to one of the NoGPO OUs will make all current updates available to that machine. If there are any pending Upgrades, the next reboot may take significantly longer than expected!