Just an FYI that I’ve started tracking Ninite and Windows updates. Expect to see an update every Tuesday detailing application version updates and any issues that crop up during my testing. Also, I discovered that our SCCM Ninite updater didn’t have 7-Zip and Notepad++ properly defined with quotations. Those should now be getting updated properly.
I went in to fix a typo on the wireless helpdoc (at http://oregonstate.edu/helpdocs/network/wireless) and realized the doc needed some serious changes.
• OUS: Removed the reference to OUS, since that entity is going away.
• Wifi Map: Removed the link to the campus wifi map because that map is defunct and the network team has asked CWS to take it down. Please don’t tell people to reference the wifi map anymore.
• OSU_Secure: We want to encourage people to use OSU_Secure. WPA works a lot better than it used to. I updated some of the language about OSU_Secure and put “(recommended)” next to it in the list of networks.
• EduRoam: EduRoam can be used by OSU people at OSU and elsewhere. Also, I think it is the preferred way to connect at PSU and UO now. (I am not even sure if the reciprocal auth stuff that we used to have in place is working anymore – need to follow up on that and possibly remove that whole section of the doc.) FYI: people can just connect to EduRoam all the time, here and elsewhere. It’s actually a really good idea, because then they will already have the cert accepted, and not have problems connecting when they travel. In fact, their device will automatically connect them to EduRoam as they travel, which is pretty cool. EduRoam at OSU is exactly like OSU_Secure in terms of features, FYI.
• I simplified some of the language in the doc and removed some things that sounded out of date.
For later: eventually we’ll want to replace “ONID account” in this doc with “OSU ID” or “OSU Login” or whatever the Identity team decides we are going to call it; but it’s too soon to make that change.
Johan wanted to see a few more changes as well, but they are mostly cosmetic.
Office 2013 is being pushed to the Extension Administration group in Ballard tonight – Tuesday May 12th, 2015.
All goes well, they should have Office 2013 tomorrow morning.
Wayne Jardine is working with Mike Akey and Lucas Turpin to remove all of the Extension and AES domains out of Cyder.
He is setting an evening for the migration of those hosts. Once that is completed, all other domains will no longer be an option.
For DOMAIN, please use “tss.oregonstate.edu”.
The user principal name will be changing for IS employees with unified accounts the evening of 5/7. The following message went out to folks who would be impacted by the change:
We need to make a change to all existing unified accounts. This will be occurring the evening of 5/7, around 9:30pm. Details are below:
The user principal name on your account will be changing from email@example.com to firstname.lastname@example.org. This does not impact your e-mail address, but does impact trying to log in to a service or computer with the old email@example.com format.
Recently the Identity & Access Management (IAM) team made a final recommendation going forward regarding the User Principal Name (UPN) format for unified accounts. While the UPN is not something that many are directly familiar with, it determines how the username must be formatted for access to many services. If you would like specifics, you can read IAM’s full breakdown here: UPN Format Decision Document.
We will be adjusting the UPN of your account to match this new standard on Thursday evening (5/7/2015). After this time valid formats for your username will be:
- UPN (ONIDUsername@oregonstate.edug. firstname.lastname@example.org)
- Domain\Username (e.g. onid\smithm)
- Some services (such as VPN) will ask just for “ONID Username” e.g. smithm
The most common things that are impacted by the UPN change are:
- Mobile devices will need to be configured to use onid\username or email@example.com as the username after the change. On some android devices, the account needs to be completely removed and added back (if the device doesn’t allow changing the username on an existing account)
- If you log in to a windows box using the firstname.lastname@example.org format and lock the workstation, you will not be able to unlock the workstation after the change. Either log out before you leave for the day, or make sure you’re logged in using onid\username.
- You will lose access to data in Office 365 when the change happens, until the next time the synchronization process runs (3am and 3pm)
- Outlook 2011 for OSX typically needs the username adjusted from the old UPN format to the new UPN format.
If you have any questions, please let me know!
We went through this process already with Client Services staff with unified accounts with minimal impact, so I don’t imagine we’ll get many calls on this.
For those that are interested,
I was doing some digging and found the release schedule for chrome and firefox. Chrome version 44 comes out May 15th, with version 45 following on June 26th. Firefox ESR version 38 will be released on May 19th, support for version 31 will end on August 11th.
If you would like to reference this information and look at more future date information.