Performing Hardware\Software Inventory - SCCM 2007
Performing Hardware\Software Inventory
Doing a hardware or software inventory can be for a server platform, Client platform or mobile platform. In this session we will see how to do a hardware\software inventory for the client platform.
So far what we have covered:
Introduction to System Central Configuration Manager 2007
Installation of System Center Configuration Manager 2007
Installation and Configuration of Secondary Site Server - SCCM 2007
Configuring Boundary and Discovery for the server & Client Platform - SCCM 2007
In this session we will see how to do inventory. Basically in a lay man language what I understand is, inventory means keeping the track or information about the computers which are discovered, why we need this just because to keep a standard environment, having a track of software or hardware installed and that is also licensed one.
How the inventory happen for the client\server machine?
There is will one service running on each machine called as “Smart Host”. This service use to pull the information and update the respective mentor, Mentor can be either a secondary site server or primary site server.
Now inorder to have this smart host service enable and approved by the site server we need to have client software installed on the respective computer.
For doing hardware\software inventories:
> I have winXP in Default-First-Site-Name and Vista in Site2
You might be thinking, why I took 2 client machine even I can explain the same thing by having one client, In windows XP we can install client software pretty easily because by default C drive is shared for the admin account i.e \\XP\C$ but if we try to install client software for Vista it won’t because by default C$ is not enabled so here we need to make some minor changes and I did some workaround as well. Will see those changes now
Installing the client software on WinxP from Primary Site Server: Firstly check that whether you are able to access the C drive of Winxp.
Log on to Primary Site server
Click on Start => Run => 192.168.1.4\c$ (where 192.168.1.4 is my windows xp computer name.
Open the SCCM console
Expand Site Database
Expand Computer Management
Expand Collections
Click on “All Desktops & servers
Right click windows XP computer name and Click on “Install Client”
Figure 1:
It will display “client push installation wizard” and next
Figure 2:
The next screen will be Installation option select: Include domain controllers, Include only clients in this site’s boundaries and also always install
Figure 3:
Then it will give us the installation details: Resource ID, object name etc.
Figure 4:
Once you run this one log will be created under windows xp : Location – C:\windows\system32\ccmsetup\ccmsetup.log. And even one service will added under windows XP
Figure 5:
This will take a long time to install the software
After the installation of Client Software
Figure 6:
In the above figure you can see the Approved status and client status.
Now in windows XP => control panel, we get one more icon called as configuration Manager
Figure 7:
It is displaying the general information, components tab, Action tab – It is nothing but which are the actions can be performed on these computer. Etc.
Installing Client Software on Windows Vista:
By default C$ is not shared in vista system, however I am not sure about \Admin$ as well. This \\192.168.0.4\admin$ is used for sharing.
Figure 8:
However by default File and print sharing is set to off so we need to set it to on.
, inorder to do share it
Click on Start => Network => Network and Sharing Center and Enable File Sharing
Figure 9:
Then we need to allow some of the ports on windows firewall inorder to do this, in the above page left side below corner we have window firewall option, just click on that => Change Setting => Windows Firewall Setting => Exemption
Enable Bits Peercaching, Dcom_TCP135, Remote Administration, SNMP Trap, Windows Firewall Remote Management, WMI & windows Remote Management
Figure 10:
> Once you are done with this – reboot the computer.
> Open the firewall log C:\windows\System32\Logfiles\Firewall – to see any ports is being blocked when you are performing the client installation software.
> Open the CCM.log on the Secondary Site Server.
> Now install the Client Software as like we did for Winxp.
> It should work but there might be chance where you won’t see any progress so open the CCM.log and check out the error, from my experience I saw Error code 5 which means access denied. So in this scenario I disabled the Firewall (testing purpose) and then I got it worked.
> Once it start to work it will create a folder CCMSetup folder under this you will get CCMsetup.log => Open it
You might notice this error message “BITS version check will not be run on Vista.” & “Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)”
I have noticed this error in my lab so my last option was:
> Log on to Vista machine
> Locate to C:\Windows\System32\CCMSetup\CCMSetup.exe, simply double click it.
Figure 11:
Just a brief overview for vista client:
Install client software from secondary site server
Check CCM log in Secondary Site Server
Unblock BITS, WMI and other service in vista and Enable File and print sharing
Try to access \\vista-machine\Admin$ (it should access)
Try to disable the firewall and try to install client software (90% of the time it will work)
Then finally would be running CCMSetup.exe from the client.
In my scenario I followed the above steps and finally I end up with running ccmsetup.exe from my client machine
Figure 12:
Performing Hardware\Software Inventory
Expand Site Database
Expand Computer Management
All Desktops and Server
Right click Winxp => Start => Resource Explorer
Figure 13:
Now it will open a new window called as Resource Explorer, Expand it you will get 3 options – Hardware, Hardware History and Software
So I am just expanding Hardware => Add\Remove Programs:
Figure 14:
Hope this article is being very informative to you all. Thanks for your time in this matter.
Ref by : http://exchangeserverinfo.com/2008/05/05/performing-hardwaresoftware-inventory--sccm-2007.aspx
Doing a hardware or software inventory can be for a server platform, Client platform or mobile platform. In this session we will see how to do a hardware\software inventory for the client platform.
So far what we have covered:
Introduction to System Central Configuration Manager 2007
Installation of System Center Configuration Manager 2007
Installation and Configuration of Secondary Site Server - SCCM 2007
Configuring Boundary and Discovery for the server & Client Platform - SCCM 2007
In this session we will see how to do inventory. Basically in a lay man language what I understand is, inventory means keeping the track or information about the computers which are discovered, why we need this just because to keep a standard environment, having a track of software or hardware installed and that is also licensed one.
How the inventory happen for the client\server machine?
There is will one service running on each machine called as “Smart Host”. This service use to pull the information and update the respective mentor, Mentor can be either a secondary site server or primary site server.
Now inorder to have this smart host service enable and approved by the site server we need to have client software installed on the respective computer.
For doing hardware\software inventories:
> I have winXP in Default-First-Site-Name and Vista in Site2
You might be thinking, why I took 2 client machine even I can explain the same thing by having one client, In windows XP we can install client software pretty easily because by default C drive is shared for the admin account i.e \\XP\C$ but if we try to install client software for Vista it won’t because by default C$ is not enabled so here we need to make some minor changes and I did some workaround as well. Will see those changes now
Installing the client software on WinxP from Primary Site Server: Firstly check that whether you are able to access the C drive of Winxp.
Log on to Primary Site server
Click on Start => Run => 192.168.1.4\c$ (where 192.168.1.4 is my windows xp computer name.
Open the SCCM console
Expand Site Database
Expand Computer Management
Expand Collections
Click on “All Desktops & servers
Right click windows XP computer name and Click on “Install Client”
Figure 1:
It will display “client push installation wizard” and next
Figure 2:
The next screen will be Installation option select: Include domain controllers, Include only clients in this site’s boundaries and also always install
Figure 3:
Then it will give us the installation details: Resource ID, object name etc.
Figure 4:
Once you run this one log will be created under windows xp : Location – C:\windows\system32\ccmsetup\ccmsetup.log. And even one service will added under windows XP
Figure 5:
This will take a long time to install the software
After the installation of Client Software
Figure 6:
In the above figure you can see the Approved status and client status.
Now in windows XP => control panel, we get one more icon called as configuration Manager
Figure 7:
It is displaying the general information, components tab, Action tab – It is nothing but which are the actions can be performed on these computer. Etc.
Installing Client Software on Windows Vista:
By default C$ is not shared in vista system, however I am not sure about \Admin$ as well. This \\192.168.0.4\admin$ is used for sharing.
Figure 8:
However by default File and print sharing is set to off so we need to set it to on.
, inorder to do share it
Click on Start => Network => Network and Sharing Center and Enable File Sharing
Figure 9:
Then we need to allow some of the ports on windows firewall inorder to do this, in the above page left side below corner we have window firewall option, just click on that => Change Setting => Windows Firewall Setting => Exemption
Enable Bits Peercaching, Dcom_TCP135, Remote Administration, SNMP Trap, Windows Firewall Remote Management, WMI & windows Remote Management
Figure 10:
> Once you are done with this – reboot the computer.
> Open the firewall log C:\windows\System32\Logfiles\Firewall – to see any ports is being blocked when you are performing the client installation software.
> Open the CCM.log on the Secondary Site Server.
> Now install the Client Software as like we did for Winxp.
> It should work but there might be chance where you won’t see any progress so open the CCM.log and check out the error, from my experience I saw Error code 5 which means access denied. So in this scenario I disabled the Firewall (testing purpose) and then I got it worked.
> Once it start to work it will create a folder CCMSetup folder under this you will get CCMsetup.log => Open it
You might notice this error message “BITS version check will not be run on Vista.” & “Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)”
I have noticed this error in my lab so my last option was:
> Log on to Vista machine
> Locate to C:\Windows\System32\CCMSetup\CCMSetup.exe, simply double click it.
Figure 11:
Just a brief overview for vista client:
Install client software from secondary site server
Check CCM log in Secondary Site Server
Unblock BITS, WMI and other service in vista and Enable File and print sharing
Try to access \\vista-machine\Admin$ (it should access)
Try to disable the firewall and try to install client software (90% of the time it will work)
Then finally would be running CCMSetup.exe from the client.
In my scenario I followed the above steps and finally I end up with running ccmsetup.exe from my client machine
Figure 12:
Performing Hardware\Software Inventory
Expand Site Database
Expand Computer Management
All Desktops and Server
Right click Winxp => Start => Resource Explorer
Figure 13:
Now it will open a new window called as Resource Explorer, Expand it you will get 3 options – Hardware, Hardware History and Software
So I am just expanding Hardware => Add\Remove Programs:
Figure 14:
Hope this article is being very informative to you all. Thanks for your time in this matter.
Ref by : http://exchangeserverinfo.com/2008/05/05/performing-hardwaresoftware-inventory--sccm-2007.aspx
