When we where looking into Office 365, on the ADFS login screen, we found we would prefer it if the user could login with the network username instead of email address. This is so it matches the rest of our services. with Active Directory Federated Services 3 we found on Server 2012 R2 wouldn't allow us to do this out of the box. The next closest thing was logging in with domain\username format.
However thanks to users on the Microsoft forum i have put some
I have just upgraded to version 9.8 of the Ruckus Firmware. But at first I got this error message after the upgrade had finished - "A support upgrade entitlement does not appear to have been purchased for this ZD. Please contact Ruckus Support further assistance. [What's this?]"
It seemed that the filtering was stopping my ZoneDirector calling back home. To resolve this issue I added the IP address 18.104.22.168 to the authentication exception in order to get
Many of us find it a little annoying that SIMS doesn't come with an .msi installer. But not to worry I have put together a script to do the job. To get yourself setup follow the following setps.
- Download the attached .zip file
- Inside the root of the source folder populate it with the following installer files SIMSAMPARKSetup.exe, SIMSApplicationSetup.exe, SIMSInfrastructureSetup.exe & SIMSManualSetup.exe
- Also inside the same folder put your connect.ini file. If you do have
I thought I would do a quick post to let you guys know about a problem we have been having.
We recently moved our SCCM server to a Server 2012 box from a Server 2008 R2 box. Once we moved during OSD we where getting random hash miss-match errors (error 0x80091007 during OSD). It was very random and happened at different times. There was nothing wrong with our packages. If you set OSD off in a VM it worked every time.
It turned out there seems to be
For those who have just upgraded to the final release of SP1 you will have found the client needs an upgrade. You can do this my one if these methods:
1. Auto upgrade SCCM 2012 Clients
2. Use the client upgrade package
Step 1 would be easier, but for devices that go offline for long periods will not upgrade as well. If you use the deployment package and let the software install outside of maintenance windows it will get to all your machines better. Also step 1 will