In the first part I explained how you can connect your Azure RemoteApp instances to Azure Operational Insights. You can find this blogpost here. In this blogpost I want to show you which Solutions are very usefull and which give you a great insight in your Azure RemoteApp environment in terms of management. In a hybrid scenario it’s your own responsibility to protect and maintain your environment. OpInsight can help you with giving you insights in what actions are needed for your Azure RemoteApp environment. The following solutions will be covered by this blogpost: Malware Assessment, System Update Assessment and Change Tracking.
WSUS
Caution: KB2506143 and KB2506146 possible issues with ConfigMgr 2012
StandardLast week Microsoft released the updates KB2506143 and KB2506146 through Windows Update. Caution with installing these updates when using Configuration Manager 2012. After installing this update you could end up with broken clients and/or servers. The client health check on clients will show the following error in the console:
Servers not showing up in WSUS
StandardToday I had some servers which weren’t visible in WSUS. So I searched on the internet and found that the following steps will solve these problems:
1 . Delete the corresponding Reg Key’s:
HKLMSOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateAccountDomainSid HKLMSOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdatePingID HKLMSOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateSusClientId
2. Restart the WSUS Client service:
net stop wuauserv net start wuauserv
3. Finally reset the WSUS settings and detect new updates:
wuauclt.exe /resetauthorization /detectnow
Migration WSUS database SQL2005 -> SQL2008
StandardToday I installed my first Microsoft SQL 2008 server. I used Windows 2008 R2 as the underlaying OS. The installation was no problem so I decided to start with the migration of one of my SQL2005 Databases, the WSUS Database.
I searched the internet for documentation about it. But most of the information is about migrating the whole WSUS server. So I decided to give it a go on some information which I found for SCOM 2007. I did the following steps:
1. Stop WSUS and IIS services on you WSUS Server
2. I did a Detach on the SUSDB database on my SQL 2005 server
3. I moved the both the DATA and LOG file to my new SQL 2008 server
4. I did a Attach on the SUSDB database on my SQL 2008 server
5. I added a login on my SQL2008 server for the Computer Account on which the Update Services is running.
6. I edited the following REG key on my WSUS Server:
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdate ServicesServerSetup] "SqlServerName"= "YOUR SQL 2008 Server"
7. Start WSUS and IIS services on you WSUS Server
After the it didn’t work for me, after the SQL 2008 Installation I forgot to configure my firewall to allow SQL traffic. So I added the following Inbound Rules to the firewall:
TCP - 135 – Transact SQL Debugger TCP - 1433 – SQL Traffic UDP - 1434 – SQL Browser Traffic TCP - 2383 – SQL Analytics Traffic TCP - 4022 – SQL Broker Traffic
After adding these rules everything works fine.