A customer of mine recently started deploying Windows 8 in their environment. MDT was set up and the deployment was working fine, but after deployment the Windows 8 machines wouldn’t connect to the WSUS server.
When trying to connect to the WSUS-server through the Control Panel I got an error message.
You can install the Azure module directly from the PowerShell prompt and connect to the numerous services offered by Microsofts extensive cloud solution!
There are numerous backup solutions out there for Windows and they come in many different forms.
There are two “types” of backup supported by the “Windows Backup and Restore Center” (WBRC).
The GUI at Microsoft is great but sometimes we need to dig a bit deeper.
I ran into some issues with a Resource mailbox and had to do some troubleshooting in the Office 365 service.
Do you ever get that sinking feeling, when you’ve forgotten the root password to your test lab? Again?
I hate it too! So I decided to figure out a way around it, using a work around…
Lately I’ve been struggling with deploying Windows via SCCM 2012 to a workstation running a RevoDrive as primary storage. The MDT scripts do not seem to think that the card is bootable…
I ran into this issue when switching between our production and test environment. If you’re receiving the 0x87D00607 error you are most likely connected to a network/site which does not have a Configuration Manager Boundary or Boundary Group.
If you’re having trouble deploying the SCCM client and you’re getting Error 53 you should verify that the Client Installation account is local administrator and that Remote administration is turned on.
I started my day troubleshooting a Windows 7 SP1 client which couldn’t install a specific printer. After verifying that the server was not the issue I started looking into the computer configuration…
You might see content mismatch warnings in System Center 2012 Configuration Manager when content validation runs and determines that there is a discrepancy between the expected list of packages in WMI on the distribution point and the packages in the content library.
