Category Archives: Base

Feedback Request: AdBlock Pro on Images

I’m looking for some feedback as to opinions regarding the installation of AdBlock Pro on our images.

The primary reasoning behind this would be to limit the amount of malware that is being installed via ads on websites. CN spends and exceptional amount of time  supporting an issue that could potential be avoided.

What do you think? Do you see any program management issues or potential software conflicts?

Please leave your thoughts in the comments. Thanks.

Office 2013 Live on Bench Images

Office 2013 is now the standard on all images coming from the Build Bench. Please let me know if customers encounter any oddities that we can address.

Additionally, if a user insists on Office 2010, please take extra steps on the interview sheet to make note of that. Until the interview sheets are updated the bench will assume 2010=2013 unless it is clearly communicated that the customer want Office 2010.

Limited Operations at Bench on 2/26 – Update

Telecom will be rewiring the network jacks on February 26, 2015.

During this time the Bench will be at limited to no functionality.

I will add to this post when I have more information.


Update!

We will have some functionality that day, but it will be limited.

What we can do:

Windows 7 Deployments from Ballard Hall

What we cannot do that day:

Backups

  • Win 8 Deployments
  • Mac Deployments
  • Everything else

I do not expect to be down for the entirety of the day, but I cannot make any guarantees. I fully expect to be back up and completely functional by the next day.

Additionally, we will have loaners prepped and ready for that day if the need arises for them.

I will be at the Bench all day while a few students will be placed over at Ballard Hall to help keep processes moving along. The rest of the Bench students will be visiting other functional areas that day for cross training. Arrangements for this are in progress and will be communicated once finalized.

Please let me know if you have any questions.

 

Follow-Up – Student Worker P: drives

After further discussion, the decision has been made to not provide Home folders to student workers as standard practice.  Departments can request a Home folder for a student worker, but they need to be aware that they will be charged for the storage space.  Work is currently underway to clean up existing P: drives; these will be addressed individually with the owning departments by the Accounts team.

Moving forward, any student worker account that does need a Home folder will need to have Exchange Attribute 7 set to “StudentHomeFolder.”  Please let me know if you have questions or concerns.

No Home folders for Student Workers after all

The decision has been made to not create Home folders for Student Workers as standard.  If a department specifically requests a Home folder for a student worker that can be done, but the department will need to be aware that they will be charged for the storage space.

We are currently doing cleanup on Student Worker accounts and removing existing Home folders that do not currently have any data. Those Home folders that do have data will be addressed individually.

Any student worker that does need to have a Home folder will need to have Exchange Attribute 7 marked with “StudentHomeFolder.”

Notice – OWA Planned Upgrade

via Jason Appah

Just some info on a minor change to Outlook Web App so you all are aware and prepared for when it happens. The log in page will be changed up a bit, now reflecting the more current Outlook style:
OWA upgrade login
The log in form works exactly the same. You may either use your Domain\user or first.last@oregonstate.edu to log in. The changes are merely aesthetic, but may cause some confusion to users. The instructions to getting there are the same as well; exmail.oregonstate.edu -> Exchange Outlook Web App. The HelpDocs page will also be updated when this change is made, and will include screenshots and examples. You may direct users to this if they have questions.

Currently the plan is to push this change out on February 15th, at about 10:00PM.

Policy Change – OSU Secure

On Tuesday, February 3rd at 5pm, a TSS domain-wide policy for OSU_Secure wireless will be deployed. What this does is create a wireless profile for OSU_Secure, sets it as the default profile and makes it available prior to Windows logon. Users will have the option to switch to OSU_Access if needed. OSU Extension has been excluded from this change due to potential issues with older access points. Additionally, Microsoft Surface tablets will be excluded from this change due to issues with wireless drivers that do notproperly support Cisco PEAP authentication.

See the link for documentation and troubleshooting details: OSU_Secure GPO Information

Policy Change – WIMs on Computers

The Bench team is no longer placing the entire WIM on the user’s computer. The reasons for this are as follows:

  • Space – WIM files get excessively huge and take up a considerable amount of hard drive space.
  • SCEP – SCEP has issues and will commonly break/fail/time out when it tries to scan the WIM file.
  • Time – We can save an incredible amount of time by not copying the file over.
  • Access – With our new DISM based capture process, a user needs the beta version of 7z to access the WIM. Since this is not a standard application on the machine, having a WIM on a computer that can’t access it makes no sense.

So what will be in CN Backup?

  • User Profile(s) associated with whom the machine is for.
  • Non-standard folders located on the root of C:\
  • Data Warehouse files when they are identified.

What happens if a computer is placed and there are additional files that are needed?

  • Call the Bench and have them place the file(s) in a location to transfer them to the user.

As a final reminder, we keep all backups for 30 days after the ticket is closed out. Once a month, on average, I go through or stored backups and clean them up.

If for some reason a backup needs to be held onto for an extended period of time, please let a Bench time member know this so that they can tag the backup as “Keep”.  All backups marked this way are then held onto for 9 months, at which time they are reviewed to determine if they need to be kept longer.