I’m currently setting up a controlled WiFi network to adhere to my parent company’s standards. We’re using the HP MSM760 controller with MSM460 access points.
I had everything set up and tested within my head office environment, however I ran into an issue when I moved the AP’s to a branch office on a different subnet.
Every AP that I moved registered with the MSM controller in Australia rather than Canada where I am. After some reading of the manual I determined it did this because the discovery of the controller works in this order:
- UPD broadcast
- DHCP options
- DNS lookup (to cnsrv1)
Because the Australian controller predates mine, they had already set up and used the DNS name “cnsrv1″. Since my APs no longer detected a controller through the UDP broadcast because of the new subnet, it resolved the DNS name and re-registered.
To move my APs back to my controller I had to do the following:
From the Australian controller, change the AP to Autonomous mode:
Then I checked my DHCP server for the current IP of the AP, because it changed after switching to autonomous mode
Following that, I logged onto the web interface of the AP.
Then I used Maintenance > System > Provision to enter the static provisioning settings:
I enabled discovery, enabled discovery by IP, and entered my Canada controller IP and clicked save:
Then from the left side of the screen, clicked Restart to confirm the static provision:
When the AP came back up, it registered on my Canada controller and all is good!
I’m in the process of configuring DPM to back up my Hyper-V environment, which resides on an EqualLogic PS6500ES SAN.
It was during this that I encountered an issue with the DPM consistency check for a 3TB VM locking up every other VM on my cluster, due to high write latencies. During this period I couldn’t even get useful stats out of the EqualLogic because SANHQ wouldn’t communicate with it and the Group Manager live sessions would fail to initialize.
After some investigation, I did the following on all my Hyper-V hosts and my DPM host:
- Disabled “Large Send Offload” for every NIC
- Set “Receive Side Scaling” queues to 8
- Disabled the Nagle algorithm for iSCSI NICs (http://social.technet.microsoft.com/wiki/contents/articles/7636.iscsi-and-the-nagle-algorithm.aspx)
- Update Broadcom firmware and drivers
Following these changes, I still see very high write latency on my backup datastore volume, but the other volumes operate perfectly.
I’m currently in the process of upgrading a standalone Server 2012 machine running Hyper-V to Server 2012 R2.
Due to resource constraints, I’m performing an in-place upgrade, despite this server residing 800km away from me. Thank goodness for iDRAC Enterprise.
However, during this process, during the “Getting Devices Ready” section I received a Blue Screen Of Death, with the error message:
After it hit this BSOD twice, the upgrade process failed out and reverted back to Server 2012. I was unable to find a log file of what occurred in any more detail, and was worried that I would be stuck on Server 2012.
Thankfully, I discovered a log file on the iDRAC with the following message:
A bus fatal error was detected on a component at slot 1.
This triggered my memory, and I recalled that we have a USB3 PCI-E card installed for pre-seeding an external drive with backup info.
I used the BIOS setup (Integrated Devices > Slot Disablement) to disable Slot 1, and then retried the upgrade with fingers crossed.
I have never attended Microsoft TechEd, but I REALLY want to, especially after seeing the sheer number of sessions that are relevant to me in 2013.
I’ve been keeping an eye on the TechEd website for some time after the event closed, watching for the posting of the recorded sessions, and now they are up, all 60 something pages of them.
I’ve gone through the list of every session, and collected a link list of 59 of them I want to watch, with some standouts like:
- Windows PowerShell unplugged
- How many coffee’s can you drink while your PC starts
- DFSR 2012 R2 enhancements
- Storage Efficiency with Dell and Storage Spaces
- Mark Russinovich on Cloud Computing
- Upgrade your IT skills and Infrastructure: Cloud Computing
- Performance Optimize your ASP.NET
- O365 Identity Management
- What’s new in Windows 8.1 Deployment
- Hyper-V Recovery Manager
- Backup Strategy for Private Cloud
And so much more…
One of the other major deployments I’ve done recently has been a refresh of all our Autodesk products to the 2014 version. In scope this was smaller than my Office 2013 deployment, however it was much more complicated.
First, I created Active Directory groups to contain the computer accounts of workstations needing a product. For example, a group for AutoCAD 2014 Network license containing computer accounts that required it for installation.
These groups were then targeted with Group Policy Objects which set a scheduled task to run the installation script at 3:00am. Due to the size of the installation, I don’t want to have this run as a startup script.
Next I needed to create the installation script.
To start, I created an Autodesk deployment through Setup.exe. This is typically how standardized installations of Autodesk products are performed, but usually aren’t enough to have a user fully set up.
I began with a deployment of Infrastructure Design Suite Premium (IDSP) since it was 40GB and contained the install files for every ‘lower-tier’ product we were going to install. This way you can use a single source of installation files but multiple configured deployments.
Once the deployment package was created, I put it into a VBS script with a WHOLE lot of other logic.
My installation script can be downloaded here: AutoCAD_2014_Network_Install(rename to .vbs)
The Uninstall Products script can be downloaded here: UninstallProducts(rename to .vbs)
The Copy Fonts script can be downloaded here: CopyFonts(rename to .vbs)
The script can be summarized as follows:
- Check default gateway on the NIC, and if matching branch offices change the install source
- Check for the acad.exe file in the installation directory, and proceed if it doesn’t exist yet
- Run the UninstallProducts script to remove previous versions of software
- Run the Autodesk deployment through the .lnk file created from Autodesk setup.exe
- Begin a loop which checks for setup.exe in the running processes.
- Wait 2 minutes before proceeding with the loop
- Once setup.exe is no longer running, continue by deleting unnecessary shortcuts
- Add extra shortcuts that point to a specific ARG file for customizations
- Install additional programs (AcroPlot PDF software in this case)
- Run the CopyFonts script, passing in the Fonts path for this particular product
- This copies required fonts to C:\Windows\Fonts and the installation directory
- Check again for acad.exe, and if it now exists then log success, otherwise log failure.