Monthly Archives: March 2015

All Groups

Printing & Mailing move status

Leave a comment

P&M move status update, as of 3/30/15 per Ben Shields:

  • Xerox 1000 (which replaced the iGen) and TR (the box that drives S1/S2) are all up and running
  • Ricoh color printer (C900?) still being worked on by vendor.
  • S2 is “up and running” but needs a part replaced (normal maintenance). Staff that use the S1/S2 are aware of this.
  • The following area are waiting on power, network, or furniture:
    • The “Secure Print” area (DVD burners, Kofax scanners)
    • Front reception desk
  • Wireless is still in progress, pending contractors completing work
  • Ben believes the printers are repointed and tested, but in case anyone calls in:
    • The Xerox 1000 is 128.193.127.25
    • The TR (S1 and S2 print queues) is 10.130.92.127
    • The iR3351 in the office area (“Customer service area”) is 10.130.92.104
    • The iR3351 in the production mailing area is 10.130.92.126
  • Holes in the firewall have been punched such that:
    • Print traffic from 128.193.25.x (Old P&M IP space, P&M Express Stop IP space) can get to the 10.130.x.y P&M hosts
    • Print traffic from 128.193.127.x (P&M Nypro public facing hosts) can get to the 10.130.x.y P&M hosts
All Groups

New Banner and AppWorx support procedures

Leave a comment

For Banner and AppWorx support, Enterprise Computing Services will now have one person assigned as the weekly Support Rep and one person as the backup Support Rep.  In order of preference, the way to get Banner and Appworx help is as follows:

  1. Open an ACTWON Service Request with a type of “ACT_HelpDesk”.  Attach all relevant screen prints, problem descriptions, and output results.
  2. If the requestor does not have ACTWON access, send an email to: ACT_Support@lists.oregonstate.edu with attached screen prints, problem descriptions, and output results.
  3. Or, as a last resort, contact the Service Rep directly.
All Groups

Mac Self Service

1 Comment

A couple of things about the Self Service app that is deployed to the Macs.

In case you have not looked at the Self Service app, please jump on a Mac and have a quick look so that you can see what it looks like.

  • Anybody who wants to use Self Service will need to use their ONID credentials to log in to Self Service (do not qualify your username with onid\ as Casper does not like domain qualifications).
  • If a customer is having trouble accessing Self Service and they have their ONID credentials correct, the machine is most likely not collected in Casper, in which case, the machine will need to have the QuickAdd package run on it.
  • A customer will only be able to see whatever packages are available for the machine that they are logging into Self Service from. Package deployments are assigned per machine, not per user, so if a person can see the OS X Mavericks installer from their 10.7 machine, but not from their 10.9 machine, it’s because the package is not assigned to be deployed to their 10.9 machine.

Now, on a different note, CJ and I have already fielded a few comments about the way the deployment of the Self Service dock icon happened. While the Self Service app has been deployed to the Macs for several months, we only started talking about deploying the dock icon yesterday as we felt we finally had enough software available in Self Service to make it worth the customers’ while (nobody wants to go shopping in a store with empty shelves). While we were excited to make the Self Service app more obvious to the customers, we should have sent a notice before we started messing around with deployment of the dock icon. I was the one who activated the deployment policy and I apologize for any confusion or unnecessary questions that it may have generated as a result.

So. If we deploy something in the future that is going to be directly visible to the customer or change their user experience in an overt manner, we will follow established procedure by sending a notice to the customers and deploying on Tuesday nights in conjunction with Patch Tuesday updates.

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

James Dudzik

All Groups

Cyder migration scheduled for March 21st

Leave a comment

IT Infrastructure Services have resolved all remaining issues that have prevented release in February. They have re-scheduled the release of Cyder to March 21st. Their original announcement:

“Maintain will no longer be available as of March 21st. This software is being replaced with Cyder. All DNS and DHCP changes will need to be made within this new software after the migration is completed on the 21st.

Maintain will be taken out of service at 10am on Saturday and the final migration of data to our new system, Cyder, will begin. We estimate completion of entire migration and check-out process by 6pm or earlier – but there is the possibility it may take longer. This time-line means that neither Cyder nor Maintain will be available during most of the day on Saturday. If urgent DNS/DHCP changes are needed during this time, please email me or call the on-call number: 7-4710.

After Cyder is up and running, maintain.oregonstate.edu will present a simple page indicating that it has been replaced and will link to Cyder as well as documentation. The development instance of Cyder will be disabled, and ultimately moved to a new name (cyder-dev) to prevent confusion after deployment. The production version of Cyder will be at cyder.oregonstate.edu.”

User Guide and Reference – http://is.oregonstate.edu/it-infrastructure/net/dns-dhcp/cyder/cyder-user-guide