Configuration Manager 2007

I found this on TechNet and had to work through it to make it work. I’ve added pics and better explanations on how to add and deploy the script to work for you. I found the scripts at this URL in TechNet. http://social.technet.microsoft.com/forums/en-US/configmgrosd/thread/5924e840-eb6e-48c1-858f-766a5be625a6/

This script will detect if the current assigned value for the computer name begins with MININT, indicating that this image is bare metal image.  It then prompts the end-user to enter a new computer name.  It is primarily useful for task sequences that do both bare metal and in-place reimages.

Steps to implement the script.

1. Create a folder for your VBS script called “AskComputerName”.
   

    
    

2. Copy cscript.exe to the AskComputerName folder.
   

3. In the folder copy the VBS script to Notepad and save the file as “askcomputername.vbs”

.

Dim sNewComputerName, oTaskSequence, sTSMachineName

Set oTaskSequence = CreateObject (“Microsoft.SMS.TSEnvironment”)

‘ Get the name the computer is set to receive and truncate to first 6 letters

sTSMachineName = oTAskSequence(“_SMSTSMachineName”)

sTSMachineName  = lcase(left(sTSMachineName,6))

If sTSMachineName = “minint” Then

    ‘ The wscript.echo commands are logged in SMSTS.log for troubleshooting.

    ‘ They are not displayed to the end user.

    wscript.echo “Detected that the computer name is scheduled to receive a random value.  Prompting user to input a standard name.”

    sNewComputerName = InputBox (“Please enter a standard computer name.”, “Computer Name”, , 30,30)

    oTaskSequence(“OSDComputerName”) = sNewComputerName

    wscript.echo “Set Task Sequence variable OSDComputerName to: ” & sNewComputerName

Else

    wscript.echo “Computer set to receive a standard name, continuing as is.”

End If

4. Create an SCCM package that holds this script.  Do not create a program. Leave the program blank. Add the package to the appropriate DPs

5. Edit an existing task sequence or create a new task sequence and add a new task to Run Command Line.  Move it to occur between “Restart in Windows PE” and “Partition Disk”

6. For the task, give it the name you want.  (e.g. AskComputerName)

7. Select checkbox “Package” and then select the package created that has the script

8. In the command line section, put the name of vbscript…with the file extension!

9. Click OK

  10. When deploying an image, you will see the following box asking for the computer name.

Ok, what does this mean, how do I figure out where the problem is? Man, what a pain!

Below is an example (PIC 1) of what I’m talking about with the “Unknown”. These “Unknown” machines mean they didn’t send in the Software Update scan on the workstation to the WSUS system. Now, which machines are these? Where do I go? To answer these questions, scroll down to your REPORTING, then REPORTS section and run the following report “Scan 2 – Last scan states by site” under “Software Updates – D. Scan” category, as shown in (PIC 2). After you run the report, you’ll notice a section called “Unknown”, and now open that section and view the “Unknowns”.

To resolve this or at least figure out what’s causing your problems, do the following steps:

1. Go to the client and open the c:\windows\Windowsupdate.log. It’s best if you can open this log from a machine that has SMS Trace installed. You can view the errors much easier as shown in (PIC 3).
   
2. Next look in the c:\windows\system32\ccm\logs\WUAHandler.log and view your errors as shown in (PIC 4).
   
3. Then if everything does look good, go to look in the Statesys.log in the SCCM server logs to see if the messages have been updated on the server. If you need to run this manually, you Right Click on Software Updates then click on Run Homepage Summarization, wait a few seconds or check your Statesys.log and then refresh Software Updates and you should see the numbers change.
   
4. If none of this is working, then you need to go to the client and from the control panel –> double click on Configuration Manager –> Click on Actions tab –> Click on Software Updates Scan Cycle and click on Initiate Action. Then check if everything is updating correctly with your logs as stated in step 1 and proceeding to step 3.
   

PIC 1

PIC 2

PIC 3

PIC 4

Pretty much everyone knows when Microsoft releases their software updates every second Tuesday each month. But did you know it’s actually after 10am Pacific Time. Yes, I said Pacific Time. For you peeps that don’t know how to calculate that…that would be 11am Mountain Time, 12 Central Time, 1pm Eastern Time. Now Hawaii, well…now you just getting complicated. Who goes to Hawaii to work anyway. Do they have computers over there? (Things that make you go, Hmmm….)

For any of you that don’t believe me, check out this link to Microsoft.

http://www.microsoft.com/security/msrc/update_cycle.mspx

While I was out doing an installation at a customer I noticed I started having problems with the SQL server’s Windows Application Log. Below you will find the error and the solution on how to resolve this. This took me 3 days and a call to Microsoft to resolve this problem since I couldn’t really find any information online discussing on how to resolve this issue. I feel it’s not a common problem, but no less another problem I had to work through.

ERROR from the Windows Application log on the SQL server:

Event Type:        Failure Audit

Event Source:        MSSQLSERVER

Event Category:        (4)

Event ID:        18456

Date:                1/21/2009

Time:                5:11:36 PM

User:                FS\FS-SCCM$

Computer:        FS-SQL1

Description:

Login failed for user ‘FS\FS-SCCM$’. [CLIENT: 10.1.255.163]

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 18 48 00 00 0e 00 00 00 .H……

0008: 08 00 00 00 46 00 53 00 ….F.S.

0010: 2d 00 53 00 51 00 4c 00 begin_of_the_skype_highlighting 

00 53 00 51 00 4c 00 FREE  end_of_the_skype_highlighting -.S.Q.L.

0018: 31 00 00 00 07 00 00 00 1…….

0020: 6d 00 61 00 73 00 74 00 m.a.s.t.

0028: 65 00 72 00 00 00 e.r…

Conduct a System Center Configuration Manager Site Repair by doing the following:

• Click on Start
  
• Click on Microsoft System Center
  
• Click on Configuration Manager 2007
  
• Click on ConfigMgr Setup
  
• The Wizard will pop up
  
  • Click Next
    
  • Click Perform site maintenance or reset this Site
    
  • Click Next
    
  • Check all 3 options
    
    • Re-Apply default file and registry permissions on this site server
      
    • Modify SQL Server Configuration
      
    • Modify SMS Provider configuration
      
  • Click Next
    
  • Confirm the information and Click Next
    
  • Confirm the information and Click Next
    
  • A popup will appear asking if you would like to reinstall the provider and click YES
    
• This will then automatically go into the actions. When completed, close and restart the server.
  

While I was trying to figure out why I couldn’t get the SMSDBMON.LOG file to stop repeating this error message over and over every second and filling up my server. I was getting desperate and called into MS support. Well, I opened a ticket and they did contact me within 2 hours, but by that time I was so frustrated I decided to try SCCM SP1 (upgrade) since I already tried the “Repair Site” option with no success.

Problem:

Warning: Could not create file e:\Program Files (x86)\Microsoft Configuration Manager\inboxes\WSUSMgr.box\100.SHA, Error=3.

Solution:

Make sure you delete this role and look at the SUPSetup.LOG and make sure it’s “Uninstalled”. Then run the SCCM SP1 with UPGRADE and reboot server after the upgrade is completed. Then install the Software Update Role.

Server 2008 – The Systems Administrator has set policies to prevent this installation

Today I was onsite at a client and ran across this when trying to install WebDAV X64 on a Server 2008. I figured out how to resolve this by doing the following steps.

Error Message:

Edit registry

1. Click
   
2. Type Regedit
   
3. Click Continue
   
4. Go to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
   
5. Right click in the right pane
   
6. Click New
   
7. Click DWORD (32bit) Value
   
8. Type DisableMSI <Enter>
   
9. Reboot the server
   

Greetings everyone, today I ran across a problem with my SCCM and various other things. Basically when I uninstalled SCCM R2 SQL Reporting Services Role, I began to have errors with my Management Point and several other services, and in particular the WSUS role. So, my first steps was to uninstall WSUS and install it again. Well, with no luck when I tried to install the services, I received the error, “Unable to uninstall WSUS due to an error”. So, I tried several things including removing all registry entries containing “WSUS” (DON’T DO THIS!). That’s another Item I learned…don’t remove the WSUS Entries from the REGISTERY.

Instead, do this and you should be ok to install WSUS.

1. Download the “Windows Installer Cleanup Utility Package”
   
2. Start the application from the Start –> Programs menu
   
3. Find “WSUS 3.01…” and remove it.
   
4. Reboot the server
   
5. Now reinstall your WSUS.
   

Good luck and have fun with WSUS.

Are you having issues with configuring Asset Intelligence Synchronization Point Role on SCCM??? If you are, it’s most likely the large question, “Where do I get the CERT.PFX file?” Well, it’s usually due to trying to figure out who to contact at Microsoft. No worries now, I’m going to tell you three ways to get this file. First way is to contact Software Assurance or your Microsoft Account Rep. Second way is to let Catapult Systems configure AI for you…in fact, let Catapult System setup and configure your SCCM. Third way and confirmed by my good buddy Jason Sandys, is to wait 90 days after Windows 7 and Windows Server 2008 R2 releases for SCCM 2007 SP2. In SCCM 2007 SP2, you will not have the need for CERT.PFX file when configuring the Asset Intelligence Synchronization Role.

Here’s a few tips when configuring Asset Intelligence.

1. Make sure your server has access on port 443 to the internet.
   
2. You can manually synchronize once every 12 hours.
   
3. Make sure your hardware and software inventory are turned on within the Client Agents.
   
4. When enabling (Figure 1) this make sure this isn’t in the middle of the day or when your SQL server is at it’s peak.
   
5. This will increase the data size on SQL, so be prepared…TechNet estimates double in size.
   
6. This usually takes time to setup, so be patient like most other pieces of SCCM.
   

URL to Asset Intelligence in TechNet Library

http://technet.microsoft.com/en-us/library/cc161988.aspx

Figure 1

Have you ran across where you keep seeing PC’s show up in your Collections with duplicate names and every time you update and refresh the collection you’ll see a different set of PC’s show duplicates.

Sample

I was seeing this happen while at a customer and it turned out they imaged a machine with ghost and then used that image over and over and over. Well, if they don’t prep that machine correctly with sysprep and the have the SCCM or SMS client already installed, this will cause a problem that you could be tracking down for days.

To resolve this issue, let’s see how many duplicates you have. Create a collection and add the following 3 queries as part of the collection. Then update and refresh your collection.

Query 1

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 where ClientVersion = “2.50.4160.2000” or Client is NULL

Query 2

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 join SMS_G_System_System on

SMS_R_System.ResourceID = SMS_G_System_System.ResourceID where

SMS_R_System.Name <> SMS_G_System_System.Name

Query 3

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 where SMS_R_System.ResourceID 

in (select SMS_GH_System_System.ResourceID from SMS_G_System_System

join SMS_GH_System_System on SMS_G_System_System.ResourceID =

SMS_GH_System_System.ResourceID where SMS_G_System_System.Name <>

SMS_GH_System_System.Name)

Now you should have a list of machines showing duplicate GUIDS in your database. Just FYI, this isn’t always the most accurate, but this allows you a starting place to attach the problem.

Next let’s start attacking the problem, you know everyone has to start somewhere.

• Create some scripts to fix this issue
  
  • Create a directory called “FixMyGuids”
    
  • In that directory download the PSTOOLS from Microsoft.
    http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx
    
  • Download the Sleep.exe
    
  • Download the SMS 2003 Toolkit 2
    http://technet.microsoft.com/en-us/sms/bb676787.aspx
    

   
   

• Now create these batch files:
  
  • “CallFinalProcess.bat”
                         Call FinalProcess.bat <computer name>
                    Call FinalProcess.bat <computer name>
                    Call FinalProcess.bat <computer name>
                    Etc….
    
  • “FinalProcess.bat”
    echo starting the FixMyGuid batch file 1copy /Y D:\DATA\Package$\FixMyGUID\fixmyguid.bat \\%1\c$.\PSTools\psexec -accepteula \\%1 -u deops\<userid password> -p <enter password>/s c:\fixmyguid.bat
    
  • “FixMyGuid.bat”
    @echo off
    echo starting the FixMyGuid batch file 2
    echo copy sleep.exe file
    copy /Y \\<server name>\package$\FixMyGUID\sleep.exe %windir%
    sleep 10 /quiet
    echo copy tranguid.exe file
    copy /Y \\<server name>\package$\FixMyGUID\tranguid.exe %windir%
    rem sleep 10 /quiet
    echo copy CCMDelCert.exe file
    copy /Y \\<server name>\package$\FixMyGUID\CCMDelCert.exe %windir%
    sleep 10 /quiet
    echo running CCMDelCert to repair GUID
    %windir%\CCMDelCert.exe
    sleep 10 /quiet
    net stop ccmexec
    net start ccmexec
    rem <remove the rem only if you know a user isn’t on the workstation to reboot the workstation>
    rem @echo rebooting workstation in 20 seconds
    rem \\<server name>\package$\FixMyGUID\Pstools\PSSHUTDOWN -r -f \\<computer name>
    

     
     

• Now you have the Duplicate GUIDS collection created. Downloaded the files required to reset the GUIDS in the SMSCFG.INI file and created the scripts to download certain files and run exe’s on the workstation to resolve the issue. What I would have liked to add is the last scripts a command to restart the workstation. If your calling the script and you know that no one is on that pc, you can remove the REM commands at the end. We’re nearing the end of the process, we need do the following to prepare for deployment.
  
  • Go to SCCM Reports and run report #130 from the Duplicate GUIDS collection.
    
  • Export the list to a CSV file and clean the file up.
    
  • Then add “Call FinalProcess.bat” before the computer name as shown in #2.
    
  • Copy and Paste the list to the CallFinalProcess.bat file
    
  • Open a CMD Prompt and run CallFinalProcess.bat file form the server.
    

     
     

1. On average you’ll have to give the machines at least 5 minutes to update before you’ll see the difference on SCCM. Nothing will hurt if you would like to update and refresh the Duplicate GUID collection. Also, you may have to run the process several times throughout a week or more since some laptops will be disconnected or not turned on.
   

While upgrading workstations from SMS client to SCCM client, I ran into several workstations having WMI errors in the CCMSETUP.LOG file, specifically;

“MSI: Warning 25001. Setup failed due to unexpected circumstance. The error code is 80041001”

I was able to resolve this by following the process outlined below.

1. Uninstall the SCCM client by running “%WinDir%\System32\ccmsetup\ccmsetup.exe /uninstall”
   
2. Click on Start –> Run –> Type “services.msc” –> <enter>
   
3. Stop the “Windows Management Instrumentation” service
   
4. Open Windows Explorer and go to “%WinDir%\System32\Webm\Repository”
   
5. Rename the Repository folder to “OLDRepository”
   
6. Go back to Services.msc and start the “Windows Management Instrumentation” service
   
7. Install the SCCM client by either pushing the client or manually installing the client from the command line on the workstation.
   
8. View the “%WinDir%\System32\ccmsetup\ccmsetup.log” file to make sure the client installs as requested.
   
9. Verify the “%WinDir%\System32\Webem\Repository” folder was created.