Vroege.biz Blog

SCCM Computers/Laptops Collections

Arjan Vroege — Tue, 07 Sep 2010 12:19:16 +0000

Today I was looking for a way to group my laptops and computers based on Operating System in SCCM. This can be done through query based collections. After some searches I came to the following final query’s which did the job for me:

Computers – Windows XP

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 5.1%” and SMS_R_System.SystemOUName like “%DOMAIN/OU’s%” and SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes not in (“8″,”9″,”10″,”14″)

Computers – Windows 7

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 6.1%” and SMS_R_System.SystemOUName like “%DOMAIN/OU’s%” and SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes not in (“8″,”9″,”10″,”14″)

Laptops – Windows XP

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 5.1%” and SMS_R_System.SystemOUName like “%DOMAIN/OU’s%” and SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in (“8″,”9″,”10″,”14″)

Laptops – Windows 7

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion like “%Workstation 6.1%” and SMS_R_System.SystemOUName like “%DOMAIN/OU’s%” and SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in (“8″,”9″,”10″,”14″)

SCOM 2007 R2: Twitter you alerts with SCOM 2007 R2

Arjan Vroege — Wed, 30 Jun 2010 08:08:49 +0000

Today I read a very interesting article on the weblog of Walter Eikenboom. Walter is a dutch Guru on SCOM 2007 R2. All credits go to him of course. Posting to be found here

Windows 2008 Server-Core: Install Windows Updates

Arjan Vroege — Sat, 19 Jun 2010 22:20:49 +0000

This evening I installed my Windows 2008 r2 Server Core Active directory server. After the installation I was looking for a simple script to search, download and install Windows Updates. I found the following script on the MSDN website of Microsoft. You can view the script here. I tested it on my brand new domain controller and it works…

SCVMM 2008 R2: Error adding Windows 2008 R2 Hyper-V Server

Arjan Vroege — Wed, 16 Jun 2010 12:31:09 +0000

Yesterday I installed my System Center Virtual Machine Manager. The installation was no problem. The first thing to do was to add my Hyper-V host, running on Windows 2008 R2, to the SCVMM server. Unfortunately there came an error. I got the following error:

Error (2916)
VMM is unable to complete the request. The connection to the agent server.contoso.com was lost.
(Unknown error (0×80338012))

Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic. If the error persists, reboot server.contoso.com and then try the operation again.

After googling the error I found many possible solutions but none of them worked. My last hit before I went to sleep was the good one. The solution for my problem was the following bug: The “Win32_Service” WMI class leaks memory in Windows Server 2008 R2 and in Windows 7. I installed the hotfix from the KB article and the problem was solved

Installing App-V Dashboard

Arjan Vroege — Thu, 10 Jun 2010 17:10:06 +0000

Today I found a interesting article about the App-V Dashboard. With the dashboard you can show some interesting App-V Usage information through a graphical website. The following picture shows how users can use the Dashboard:

The Application Virtualization Dashboard process flow involves the following sequence of activities:

An IT Service Manager requests a new data set.
The IT Administrator uses the Dashboard Configuration Web Part to define the new data set.
The IT Administrator stores the configuration information for the new data set (the information is saved in the Windows SharePoint Services Content database).
The IT Administrator adds a new copy of the Dashboard Viewer Web Part to the default Application Virtualization Dashboard and then modifies the Web part to display the new data set.
The IT Service Manager browses to the Application Virtualization Dashboard site.
Windows SharePoint Services queries the Application Virtualization database as specified by the data set configuration.
Windows SharePoint Services renders the new data set using the Dashboard Viewer Web Part.

More information can be found here. The installation of the dashboard has to following requirements:

Microsoft App-V 4.5 or 4.6
Windows Sharepoint Services 3.0 SP2 or Microsoft Office SharePoint Server 2007 SP2
Microsoft .Net 3.5 Framework
Windows Internet Explorer 7 or 8

I decided to install the dashboard on the App-V Management Server for a test. I did the following installation steps:

1. Download and Install .Net 3.5 Framework
2. Download and Install Windows Sharepoint Services 3.0 SP2, choose StandAlone Install if you want to install the SQL 2005 MSDE, if you want to connect to a existing SQL Instance choose web-front end.
3. After the Installation of SPS 3.0 SP2, run the configuration wizard.
4. Download the AppVDashboard from the Connect Website of Microsoft
5. Extract the downloaded zip file
6. Open a command prompt and type the following command:

Msiexec /I AppVDashboard_x86.msi /L*V setup.log

7. Click Next on the Welcome Installation Screen
8. Click I Accept en Next
9. Fill in the information needed to connect to the database
10. Fill in the information for the Sharepoint Website
11. Click Install to Install the dashboard

After the installation the configuration must be done. More to follow….

System Center Roadmap

Arjan Vroege — Thu, 10 Jun 2010 10:26:34 +0000

At TechEd this week, Microsoft presented the Roadmap for the System Center products. The coming years will be the years of vNext versions… Very interesting. Currently SCCM vNext is in the phase of Beta 1. I am planning to install the beta in the next weeks. I will post some screens and information on my blog. For now the Roadmap (click on the image for the full image size):

Installing App-V 4.5 SP2 on 4.6 Management Server

Arjan Vroege — Fri, 28 May 2010 17:00:12 +0000

This week Microsoft released App-V 4.5 SP2. The release notes introduced the following new functions:

Support for Office 2010: App-V 4.5 SP2 now supports the virtualization of Microsoft Office 2010.
Support for Database Mirroring: App-V 4.5 SP2 now supports Microsoft SQL Server Database Mirroring.
Customer Feedback and Hotfix Rollup: App-V 4.5 SP2 also includes a rollup of fixes to address issues found after the App-V 4.5 SP1 release.

The support for database mirroring is a very interested new function. But how about database mirroring on my App-V 4.6 infrastructure. I looked at the version of my App-V 4.6 server, the version was 4.5.2.17140. So technically it’s also possible to install the servicepack on my 4.6 infrastructure. I give it a try:

I looked in my database on which version my server was runnning. I did the following query:

SELECT hostname,version FROM dbo.SERVERS;

The result was:

Hostname: ###### ——- Version: 4.5.2.17140

Below the steps I did:

1. Download the patch from here

2. Unzip the download file and start the setup_upgrade.exe from the Management Server folder

3. On the welcome screen click Next

4. Accept the terms and click Next

5. Choose your option on the Windows Update screen and click Next

6. Note that the access to the Management Server will be disbabled and click Next

7. Check if the database information is correct and click Next

8. Click Next

9. Click Upgrade

10. After the Upgrade restart the Management Server

After the restart I ran the query again:

Hostname: ###### ——- Version: 4.5.3.19480

The result is that my 4.6 App-V Management Server is upgraded with a 4.5 SP2. Very nice logic, but it works. Now it’s time for in dept testing!!

Error Installing KB974417 (.Net 2.0)

Arjan Vroege — Thu, 01 Apr 2010 08:07:22 +0000

If you get the following error while installing KB974417 through WSUS:

Installation Failure: Windows failed to install the following update with error 0×80070643: Microsoft .NET Framework 2.0 Service Pack 2 Security Update for Windows 2000, Windows Server 2003, and Windows XP (KB974417).

I posted the solution which I found on the microsoft blogs and tested:

1. Remove KB976569

2. Install KB974417

3. Reinstall other .Net Updates

Servers not showing up in WSUS

Arjan Vroege — Thu, 25 Mar 2010 13:27:52 +0000

Today 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:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AccountDomainSid
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\PingID
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId

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

Arjan Vroege — Wed, 10 Feb 2010 18:20:55 +0000

Today 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_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup]
"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.