This script will show which all IP address are in use for a range of IP and also check whihc all are online and whihc all are offline.

SCRIPT
=======

============================================================================================
'Script Written by Sudheesh Narayanaswamy
'This can be used to check the IP address which are in use currentely. It will tell you which all IP are online and which all are offline
'SET teh Minnum Rnage and Maximum range'Name the service which you want to check in the Varable sService (Name of service in uppercase)
'Usuage cscript <FILENAME.VBS> will output to dos and in case you want to save this cscript <FILENAME.VBS> output.log
'==============================================================================================

 'Set the values to test
RangeMin = " 10.171.88.136"
RangeMax = " 10.171.88.156"

Set WshShell = CreateObject("WScript.Shell")

MinAry = Split(RangeMin, ".", -1, 1)
MaxAry = Split(RangeMax, ".", -1, 1)

times =  MaxAry(3)- MinAry(3)

For i=1 To times
IPAry = Join(MinAry, ".")

PINGFlag = Not CBool(WshShell.run("ping -n 1" & IPAry ,0,True))
If PINGFlag = True Then        
WScript.Echo "Online"  & IPAry
Else
WScript.Echo "Ofline"  & IPAry 
End If
MinAry(3)=MinAry(3)+1
Next

=============================================================================

Hope this will be helpful

Sudheesh Narayanaswamy | Support Engineer

 How to install SCUP and configure

This will show the steps on how to install SCUP and also configure a third party catalogue, (EH Adobe Flash player) and deploy the clients reporting to SCCM server.

You can download the SCUP from the following link http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0446cce9-94a4-4fb0-b335-e7516044063d&displaylang=en

On the SCCM server or on any other server you can install System Center Updates Publisher.

The perquisite is to have SQL server. You can use the express installation or use any other SQL server.

Updates Publisher is supported on the following operating systems:

• ·       The Microsoft Windows® XP Professional operating system with Service Pack 2 (SP2)
• ·       The Microsoft Windows® XP Professional x64 Edition operating system
• ·       The 32-bit versions of the Microsoft Windows Server®°2003 operating systems with Service Pack 1 (SP1)
• ·       The x64-based editions of the Microsoft Windows Server®°2003 operating systems
• ·       The 32-bit versions of the Microsoft Windows Server®°2003 R2 operating systems
• ·       The x64-based editions of the Microsoft Windows Server®°2003 R2 operating systems
• ·       The Windows Vista™ operating systems
• ·       The x64-based editions of the Windows Vista™ x64 Edition operating systems

Software Requirements

• ·       Updates Publisher has the following software requirements:
• ·       Microsoft Management Console 3.0 (MMC). MMC 3.0 must be installed prior to running the Updates Publisher Setup. You can download the MMC 3.0 from the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?linkid=21788).
• ·       For Updates Publisher 4.5, WSUS 3.0 SP2SP1 Administration Console. If WSUS 3.0 SP2 is not already installed on the local computer, the WSUS 3.0 SP2 Administration Console must be installed prior to running the Updates Publisher Setup. You can download the WSUS 3.0 SP2 Administration Console from the Windows Server Update Services Web site
• ·       Microsoft Internet Explorer 6 SP1 or later. A supported version of Internet Explorer must be installed prior to running the Updates Publisher Setup. You can download Internet Explorer 6 SP1 from the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?linkid=21788).
• ·       Microsoft Windows Installer 3.1. The Updates Publisher Setup installs Windows Installer 3.1, if required.
• ·       Microsoft .NET Framework 2.0. The Updates Publisher Setup installs .NET Framework 2.0, if required.
• ·       Microsoft SQL Server 2005 SP1 or Microsoft SQL Server 2005 Express Edition SP2. The Updates Publisher Setup installs SQL Server 2005 Express Edition SP2, if required.

How to install SCUP

Double click the SystemCenterUpdatesPublisher45.exe.

Click next and it will ask to select local database or install SQL express edition. DO the same

Once clicked next it will install the perquisite and then will proceed the installation

Select The folder 

 Installation will proceed and will complete the installation

Once done complete the installation click on finish. 

How to configure SCUP

Once the installation is over open the console of SCUP.

Click on import updates from the right side. You can download the adobe flash player catalogue from the following link http://fpdownload.adobe.com/get/flashplayer/current/licensing/win/AdobeFlashPlayerCatalog_SCUP.cab

Click on Single Catalogue Import 

Point to the CAB file downloaded. 

IT will then start uploading  

 Click on Accept

 Once you have completed this you will find adobe flash player as shown below.

 Now the set the Publish flag. On the Adobe flash player select settings and then do the following configuration. Select the update server if locally installed the same one or you can select the remote in case you install SCUP.

First, you have to configure SCUP to sign patches with the WSSC.  To do that, select the settings option from the console screen

On the Update Server tab, select create to create the WSSC

Once complete, you should have a new WSSC as shown

This action creates the WSSC in the WSUS > Certificates note of the Certificates.msc as shown

So the certificate we need is now created, but we aren’t ready to go yet.  Next we have to make sure the WSSC cert is included in the Trusted Publishers > Certificates and the Trusted Root Certificate Authorities > Certificates store.Simple process to export the cert and import it to the other two stores.  To export the cert, just right click on it and select to export – take all the defaults and save the cert to a .cer file.  To import, just right click on the Trusted Publishers and Trusted Root Certificate Authorities nodes, respectively, and select to import and point to the file. 

One this is completed On the SCUP console please do the following. Click on Publish updates

Click on Accept

 Once successfully published run the Synchronization in the SCCM server

  Once the synchronization is completed the security update you would see the adobe flash layer

 Now on the SCCM server Download the update and then create a deployment

Select the DP

  Create a Deployment

 Now on the clients do the following settings

So now SCUP should be configured to sign updates with the WSSC and publish updates to the SCCM Software Update point and you can deploy them to clients.  But, the clients aren’t ready to receive them and will reject the update if it arrives.  To get the client ready to receive updates you need to transfer the WSSC to the clients certificate store as well.  You can do this manually or even through software distribution using the certutil command.

To deploy the certificate with software distribution, do the following.

1. Export the WSUS Publishers Self-signed certificate and public key to a directory on the local computer.
2. Copy the Certutil.exe and Certadm.dll files to the same directory as the exported files. Certutil.exe is a command-line program that is installed as part of Certificate Services in the Windows Server 2003 family and both files are installed in %windir%\system32, by default.
3. Create a software distribution package containing the files from step 1 and step 2. For more information, see How to Create a Package (http://go.microsoft.com/fwlink/?LinkId=108444)
4. Add a software distribution program that runs the following command-line: certutil.exe -addstore TrustedPublisher wsus.cer, where TrustedPublisher is the name of the certificate store and wsus.cer is the name of the exported certificate. For more information about creating a software distribution program, see How to Create a Program (http://go.microsoft.com/fwlink/?LinkId=108446). For more information about certutil.exe, see the Certutil Web site on TechNet (http://go.microsoft.com/fwlink/?LinkId=108447)
5. Create an advertisement for distributing the package and program to the appropriate collection. For more information, see How to Create an Advertisement (http://go.microsoft.com/fwlink/?LinkId=108449).

You may also have to include the WSSC in the Trusted Root Certificate Authorities node as well, which can be done with easy adjustments to the package if needed.  Be sure and test first to determine exactly what is needed for your environment.

Once you have the certificates deployed, now you just have to adjust local policy to allow signed cupdates from an intranet Microsoft update service location.  You can find that setting as shown below. 

To test that everything is working, deploy a SCUP patch to a test client and review the WUAHandler.log.  If all is configured properly, you should see the patch install if needed.  If there are problems you will notice errors similar to the following in the log.

In the server the updatepublisher.log in %temp% on the SCUP installed machine also help to check the error.

Hope this information would be useful

 Sudheesh Narayanaswamy

Part II : From windows PE to Full Blown OS

Once the client boots to PXE  (which we have explained in Part I ) the clients goes to the management point and get the list of policy.

If any Mandatory (required) deployment then it will go ahead with that else if it is available deployment it will show you the List of advertisement.

 From the WindowsPE and  before HDD format the sequence of events is logged in SMSTS.log in the location   x:\windows\temp\smstslog\smsts.log

 The snippet below shows which policy are retrieved which policy is downloaded and from where.  SMSTS.log are usually pretty big.

I will be pointing only the required lines rest I will attach in a ZIP file which you can look in detail.

Preparing Policy Assignment Request. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Setting transport. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Setting site code = LAB. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Setting client ID = 0496841d-c8ba-4215-bc34-94da8ad4cd12. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
   Setting site signing Certificate. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Setting SiteSigningCertificateContext TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Executing Policy Assignment Request. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Sending RequestAssignments TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Setting message signatures. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Setting the authenticator. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80  CCM_POST /ccm_system/request TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Request was succesful. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
::DecompressBuffer(65536) TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Decompression (zlib) succeeded: original size 25716, uncompressed size 120828. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Request client ID: 0496841d-c8ba-4215-bc34-94da8ad4cd12 TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Response client ID: 0496841d-c8ba-4215-bc34-94da8ad4cd12 TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Retrieving Policy Assignments: TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment {42a5d36c-1a04-4171-a34a-7d1ba6896d49}. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment {6d4fd9bd-f9a8-4225-bd76-84e25e99ea39}. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment {4bf211e4-461e-495c-aae1-cf47a73b95b2}. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
   
     ...........................

     ..............................    

    Processing Policy Assignment {adcfd522-f142-4aad-becc-a591eea01bd1}. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment LAB20000-LAB00003-3B5BFFE2. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment SRC10000. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment DEP-LAB20002-LAB00002-6F6BCC28. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment DEP-LAB20002-LAB00004-6F6BCC28. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Processing Policy Assignment DEP-LAB20002-LAB0000A-6F6BCC28. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Successfully read 43 policy assignments. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Downloading policy body LAB20002-LAB0000B-6F6BCC28. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Preparing Policy Body Request. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Setting transport. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
    Setting policy location = http://<mp>/SMS_MP/.sms_pol?LAB20002-LAB0000B-6F6BCC28.1_00. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Executing Policy Body Request. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80  GET /SMS_MP/.sms_pol?LAB20002-LAB0000B-6F6BCC28.1_00 TSPxe 20-09-2013 18:53:22 1244 (0x04DC)
Request was succesful. TSPxe 20-09-2013 18:53:22 1244 (0x04DC)

 You would also see the Network account policy which will be used to contact DP also being downloaded and evaluated

Reading Policy Body. TSPxe 20-09-2013 19:01:48 1336 (0x0538)
Parsing Policy Body. TSPxe 20-09-2013 19:01:48 1336 (0x0538)
Found NetworkAccessUsername/NetworkAccessPassword from NAAConfig CCM_NetworkAccessAccount TSPxe 20-09-2013 19:01:48 1336 (0x0538)
Network Access Account has a non-empty value TSPxe 20-09-2013 19:01:48 1336 (0x0538)
Getting local network information. TSPxe 20-09-2013 19:01:48 1336 (0x0538)

It will then check for all the content location for reference package you would find multiple occurrence of location request as below related to content reply .

If any issues with content lookup the TS would fail here and in such situations you would need to check the packages\application\boot images\OS image etc is distributed the DP which the client is assigned to.

 Request was succesful. TSPxe 20-09-2013 19:01:48 1336 (0x0538)
::DecompressBuffer(65536) TSPxe 20-09-2013 19:01:48 1336 (0x0538)
Decompression (zlib) succeeded: original size 547, uncompressed size 1690. TSPxe 20-09-2013 19:01:48 1336 (0x0538)
Location Reply: <ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="1024"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="LAB" MasterSiteCode="LAB" SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://CM2012SP1.sudilab.com/SMS_DP_SMSPKG$/LAB00004" Signature="http://CM2012SP1.sudilab.com/SMS_DP_SMSSIG$/LAB00004"/><ADSite Name="Default-First-Site-Name"/><IPSubnets><IPSubnet Address="192.168.1.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7804</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>CM2012SP1.sudilab.com</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="0"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site></Sites></ContentLocationReply> TSPxe 20-09-2013 19:01:48 1336 (0x0538)
MCS server:  TSPxe 20-09-2013 19:01:48 1336 (0x0538)
Found location: http://CM2012SP1.sudilab.com/SMS_DP_SMSPKG$/LAB00004 TSPxe 20-09-2013 19:01:48 1336 (0x0538)

Till this time TSPxe will be component in questions and once this is completed the Tasksequence is then read and parsed.

Then the Tasksequence starts performing one by one. Here on TSMager component will come in to action. This is the TS I have used which is a very basic one

Parsing group node: Install Operating System TSManager 20-09-2013 19:01:48 732 (0x02DC)
Parsing step node: Restart in Windows PE TSManager 20-09-2013 19:01:48 732 (0x02DC)
Parsing step node: Partition Disk 0 - BIOS TSManager 20-09-2013 19:01:48 732 (0x02DC)
Parsing step node: Partition Disk 0 - UEFI TSManager 20-09-2013 19:01:48 732 (0x02DC)
Parsing step node: Pre-provision BitLocker TSManager 20-09-2013 19:01:48 732 (0x02DC)
Parsing step node: Apply Operating System TSManager 20-09-2013 19:01:48 732 (0x02DC)
Parsing step node: Apply Windows Settings TSManager 20-09-2013 19:01:48 732 (0x02DC)

 Then you see the Tasksequence steps being executed

Start executing the command line: osddiskpart.exe TSManager 20-09-2013 19:01:49 732 (0x02DC)
!--------------------------------------------------------------------------------------------! TSManager 20-09-2013 19:01:49 732 (0x02DC)
Expand a string: WinPE TSManager 20-09-2013 19:01:49 732 (0x02DC)
Executing command line: osddiskpart.exe TSManager 20-09-2013 19:01:49 732 (0x02DC)
==============================[ OSDDiskPart.exe ]============================== OSDDiskPart 20-09-2013 19:01:49 852 (0x0354)
Command line: "osddiskpart.exe" OSDDiskPart 20-09-2013 19:01:49 852 (0x0354)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' OSDDiskPart 20-09-2013 19:01:49 852 (0x0354)
Reading partition size info for partition 0 OSDDiskPart 20-09-2013 19:01:49 852 (0x0354)
Remaining size before partition: 136358691840 OSDDiskPart 20-09-2013 19:01:49 852 (0x0354)
.............

............

OSDDiskPart.exe completed successfully OSDDiskPart 20-09-2013 19:02:04 852 (0x0354)
Process completed with exit code 0 TSManager 20-09-2013 19:02:04 732 (0x02DC)
!--------------------------------------------------------------------------------------------! TSManager 20-09-2013 19:02:04 732 (0x02DC)
Successfully completed the action (Partition Disk 0 - BIOS) with the exit win32 code 0 TSManager 20-09-2013 19:02:04 732 (0x02DC)

 If you filter with Successfully completed the action you can get which all completed and if any steps fails you could check the error accordingly and then troubleshoot.

Each step does different things to know in detail please check the article http://technet.microsoft.com/en-us/library/hh846237.aspx

Successfully completed the action (Partition Disk 0 - BIOS) with the exit win32 code 0 TSManager 20-09-2013 19:02:04 732 (0x02DC)
Successfully completed the action (Pre-provision BitLocker) with the exit win32 code 0 TSManager 20-09-2013 19:02:05 732 (0x02DC)
Successfully completed the action (Apply Operating System) with the exit win32 code 0 TSManager 20-09-2013 19:15:45 732 (0x02DC)
Successfully completed the action (Apply Windows Settings) with the exit win32 code 0 TSManager 20-09-2013 19:15:46 732 (0x02DC)
Successfully completed the action (Apply Network Settings) with the exit win32 code 0 TSManager 20-09-2013 19:15:46 732 (0x02DC)
Successfully completed the action (Apply Device Drivers) with the exit win32 code 0 TSManager 20-09-2013 19:18:15 732 (0x02DC)
Successfully completed the action (Setup Windows and Configuration Manager) with the exit win32 code 0 TSManager 20-09-2013 19:20:36 732 (0x02DC)

 Once these steps are completed the windows PE phase get finished and it will boot to OS which we had applied

Save the current environment block TSManager 20-09-2013 19:20:41 732 (0x02DC)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 20-09-2013 19:20:41 732 (0x02DC)
Current operating system is Windows PE. Computer will automatically rebooted when the process exits. TSManager 20-09-2013 19:21:11 732 (0x02DC)
The action (Setup Windows and Configuration Manager) initiated a reboot request TSManager 20-09-2013 19:21:11 732 (0x02DC)

You will also find the information from windows PE load to format of the disk in the SMSTS.log located at x:\smstslog\smsts.log.

Now since we have drive created and OS applied c:\_SMSTaskSequence\ which will be used as a working directory for the Tasksequence and once it is completed this will be deleted. Presence of this folder after the Tasksequence itself is a indication that TS did not complete fine.

In the windowsPE phase what ever you have in X:\  drive smsts.log will also be there in c:\_SMSTaskSequence\Logs\Smstslog\smsts.log.

Once the system boot to complete OS the X:\ data will no longer be available so you would need to grab logs before the reboot.

You can use this http://blogs.technet.com/b/sudheesn/archive/2010/03/09/how-to-get-the-related-logs-for-troubleshooting-operating-system-deployment.aspx For 2012 only the change is the location in boot image properties rest everything is the same.

Now once the system boots to full OS it will configure the OS, drivers and then install the client. In winpe only download happens till the client is installed you will find the logs in c:\_SMSTaskSequence\Logs\Smstslog\smsts.log and then it will continue through the Tasksequence if any further steps are there.

Once the client is installed then you will find the logs in the :\windows\ccm\logs\smsts.log in 2012 and in 2007 :\windows\system32\ccm\logs\smsts.log  :\windows\sysWOW64\ccm\logs\smsts.log

As you can make TS of your choice and the failure can happen any where in this it is difficult to explain all possible issues. But if you can read the smsts.log most of the issue can be sorted out as failure of any step is given in detail in the logs. What is important is that you need to find the first step failed as in many cases I had seen people looking at the last error and get misled.

For OSD issues observation , probing and finding the first major failure is the key. Just what we need to understand that when these basic steps are in place then it is just how the Tasksequence was created can make issues. In various to isolate the issue different trial and error method like disabling few steps or deleting few will make a lot of sense.

If you think TS as a step by step command thrower and approach the issues things will be simpler. If you have failure when OS is being applied , driver injection etc the other OS logs will be of help.

This link has a good collection http://technet.microsoft.com/en-us/library/dd744583(v=ws.10).aspx

I am also attaching a ZIP file with the logs which was collected while preparing this doc. For more details you can refer this.

Hope this helps

-----------------------------------

Sudheesh N

Content Lookup in configuration Manager

Whether it is Software distribution , Software updates deployment or application deployment in 2012 the Majority of the issues comes is w.r.t to the clients not getting the Contents.

This Blogs is on how we can check and find out the reason why the client is not able to get the contents.

Whenever Client needs a content it will ask its local management point for the content and management point check against the site database and return back the list of distribution point which is used by the client.

We had issues in which when we try to Open the SCCM CONSOLE we were getting the

Error message
============
"The ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site
server and SMS Provider computers. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console Connections" in ConfigMgr Help"

On the SMSADMINUI.log you will have the following information

SMSADMINUI.log
=============
Error Code:
InvalidClass
\r\nSystem.Management.ManagementException\r\nInvalid class \r\n at
System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus
errorCode)
at
System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()

at
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsO
bject.<GetEnumerator>d__0.MoveNext()\r\nManagementException details:
instance of __ExtendedStatus
{
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE
ReportingSiteCode = ''";
ProviderName = "WinMgmt";
};
\r\n
[4][8/8/2008 1:09:29 PM] :Failure while loading required 'WQL' query engine, console cannot connec

Troubleshooting

=============

For troubleshooting this issue

·         Go to start ->run -> Wbemtest

·         Cick to Connect to root\sms --> Enum Classes-->Select recursive- -->Select
SMS_ProviderLocation () Click on instances

·         In case you find that there was no entry for this, Please re-compile smsprov.mof using the command mofcomp smsprov.mof

Note: if mofcomp has to run the path needs to be set to C:\Windows\System32\wbem. SMSprov.mof will be inside the bin folder where you had installed the SCCM \program files\Microsoft Configuration Manager\bin\i386

Hope this information will be useful

Sudheesh Narayanaswamy | Support Engineer