Configuration Manager Setup/Deployment Forum

SCCM SP2 upgrade applied, windows 7 not supported?

Wed, 25 Nov 2009 23:45:52 Z

I'm running SCCM in native mode and WSUS both on a single server. I just applied SCCM SP2 (upgraded from SP1 R2) and WSUS SP2 (upgraded from SP1).
Since the upgrade I have tried without success to install the SCCM client on Windows 7 workstations. Here is a ccmsetup/log excerpt from the windows 7 machine:

<![LOG[Client OS Version is 6.1, Service Pack Version 0]LOG]!><time="16:18:31.833+420" date="11-25-2009" component="ccmsetup" context="" type="1" thread="3856" file="ccmsetup.cpp:533">
<![LOG[Client OS is not a supported Windows Embedded Platform]LOG]!><time="16:18:31.833+420" date="11-25-2009" component="ccmsetup" context="" type="1" thread="3856" file="ccmsetup.cpp:535">

I also notice that there are no default collection groups for windows 7 or windows 2008 R2, which I thought the upgrade to SP2 would have created.
Did my install of sp2 fail despite the reported success from the installer?
Why does windows 7 appear to be unsupported?

Windows 7 SCCM pxe deployement queston

Thu, 26 Nov 2009 00:59:21 Z

Currently i have SCCM sp1 with R2 running on windows server 2003 sp2 /R2..also i have MDT 2008 update1 and AIK 1.0 installed..No inder to deploy windows 7 via pxe, i under stand that i have to upgrade my sccm to sp2 but do i need to upgrade MDT to 2010 and AIK also?

thanks

Dom

Regarding SCCM SP2 Upgrade

Tue, 24 Nov 2009 01:01:58 Z

Hi Guys

Just a quick question regarding SP2 upgrade. In our environment , we are currently having SCCM SP1 and upgrading to SP2 this weekend. We are doing all sort of test these days in test environment but as tests can never be complete, just looking some guidance from you experts out there. Thanks in Advance

We have tier 3 structure as below

                CentralSite (CTS) - SCCM SP1

     Primary Site 1 (PS1)                                      Primary Site 2 (PS2)                                              Primary Site 3 (PS3)

60 Secondary Site (S01-S60)                60 Secondary Site (T01-T60)                                      60 Secondary Site (U01-U60)

As Part of first stage, We are upgrading CTS, PS1, S01 and will test OSD build, package push etc.. and after 2 days we are planning to upgrade PS2 , PS3, 5 sites from PS1, 5 Sites PS2 and 5 Sites PS3 per day for upgrade. All the corresponding sites workstation config clients will be upgraded to sp2 clients on subsequent days using group policy.

Few questions and concerns.

1.Once we Upgrade CTS -> PS1 -> C01, what will be effect on PS2, PS3 and rest of secondary sites. Will they still be able to work as they are now or will just stopped working because of different versions?

2. Is it correct to upgrade just CTS, PS1 and C01 or we should upgrade all primary sites at first place before upgrading any secondary site?

3. We have SCCM backup in place, say if something goes wrong and we revert back CTS, PS1 and C01 but before doing that as all workstation clients are upgraded, do we need to follow from bottom to top for eg. downgrading all client then C01 then PS1 then CTS. Probably, we should not worry in getting all workstations fixed but definetly C01 ->PS1 ->CTS

4. Some secondary and Primary sites are showing errors, and insuch a bug environment, there will be always sites with some issues. Should we resolve this issues first before moving or we can upgrade CTS and PS1 as far as there are no errors on this sites?

5. What all other factors we should consider before upgrading it to SP2?

Thanks in advance for all your advises

Veday

Server Engineer

Preliminary Install of SCCM 2007

Wed, 25 Nov 2009 01:06:16 Z

Hello Everyone,

Today I am tasked of upgrading our SMS2003 server and integrating it into a new SCCM7 server running Windows Server 2008. I have been reading up on SCCM in regards to preliminary requirements and I have confirmed our current infrastructure is capable for this implemenation. My question is if I were to go ahead with the install of a new SCCM 2007 server+SMS server would there be any negative impacts if I were to install one in our production environment. Unfortunately, we do not have a test environment in place and I need to proceed with the implementation as soon as possible. What kind of problems could occur by simply upgrading the schema? I would most likely be doing the schema updates after hours and would have backups of each DC in the event everything goes south.

Any recommendations would be helpful.

Note: We are using a mixture of Windows Server 2000/2003 servers in our production environment so as far as the documentation recommends, I will not be utilizing the 'Native Mode' feature-- most likely a Mixed Mode site environment.

Upgrade Clients Using Software Distribution (SMS client to SCCM client) - not working

Wed, 25 Nov 2009 22:08:34 Z

I am having an issue getting my sms clients to upgrade to sccm clients using software distribution. I am some

Here is some background. We currently have SMS in our environment and are looking to migrate to SCCM (Side by Side upgrade)

To test this scenario out I have created a lab environment which consists of a clone of our DC Server, a new SCCM R2 Server, a SQL Server, and 5 workstations with the SMS client on them. This is an isolated subnet.

The SCCM server has the following roles: The default roles plus, MP, DP, FSP, RP, SUP, and State Migration Point. This server is setup for Native Mode (certs configured and installed). Boundaries setup using IP Address Range. Workstations have been discovered using AD System Discovery
The SQL Server hosts the site DB, and is the CA
The AD Schema has been extended
The client workstations are set up without local administrator rights

I have tested a manual install using the administrator account pointing to the source CCMSetup.exe files using the following extensions: /noservice smssitecoe=reglabsccm01 fsp=reglabsccm01

I have set up a GPO for SCCM and WSUS

enables auto update, automatically downloads and installs on a schedule, specifies the MS update service location, configures both options with the value http://reglabsccm01.dom100ds01.local, checks for updates every hour

I have added in the SCCM template, enabled it and set the parameters to: /noservice smssitecode=REG FSP=REGLABSCCM01

I have created a CM Package containing the client software using the technet instructions (bits is installed on the workstations)

In the Programs, I edited the Advanced Client Silent Upgrade to have the following command line properties: CCMSetup.exe /noservice SMSSITECODE=REG fsp=reglabsccm01

I have enabled Software Update Point Client Installation

The users have Read and Execute rights to files and folders for the location of ccmsetup.exe

I am still learning SCCM so any help or tips would be appreciated

Where to set SCCM AD Discovery in a Multi Site Hierarchy

Wed, 25 Nov 2009 16:54:03 Z

I have a Central site, 16 Primary sites and 80 Secondary sites. I am wondering where I need to set the AD Discovery? At each secondary site? Or on every site (All Primary's, Secondarys and Central).

Settings missing from WMI

Wed, 11 Feb 2009 14:30:22 Z

Hi All,
Yet another question from me I'm afraid :(

I've had a bit of time recently to try getting our public network clients setup in SCCM and I've run into a problem which I can't seem to fix.

All of our public network clients are protected by Deepfreeze (think Microsoft SteadyState) which rolls back all changes done to the OS at reboot/shutdown.

First problem I got around by creating a "thawed" drive that doesn't get reverted, this is named T:\

Used this command line to install: CCMSETUP.EXE CCMINSTALLDIR="T:\SCCM" SMSCACHEDIR="T:\SCCM\Cache"

This installs the client fine, no errors in either ccmsetup.log or client.msi.log (at least none that indicate problems)
The install is done when the system is "thawed" so no changes are performed during a reboot.

Problem is once the client is installed none of the components change from an installed state to enabled and the execmgr.log has these lines in it:

Software Distribution Site Settings for the client are missing from WMI.
Common Client Agent Settings for the client are missing from WMI.

ccmexec.log is clear of errors.

So far I have tried:
uninstall/reinstall.
Forced update of policies
Rebuilt of WMI
Searching endless posts on the internet.

All of this is done while Deepfreeze is inactive, so that's not an issue yet, just mentioned it before you asked why I'm installing it to the T drive ;)

Any ideas anyone?

Cheers,
SB

http://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx If you don't ever patch anything, for god sake make sure this patch is on.......

Scripting creation of Addresses

Wed, 25 Nov 2009 16:11:59 Z

Has anyone tried using the Technet vb script for creating multiple Addresses in SMS 2003 on an SCCM site? I have a single primary site running SCCM 2007 SP2 with SQL server 2008 SP1 running on the same box. The script does successfully create the address, but on the Rate Limits tab, 'Unlimited when sending to this address' is selected instead of 'Limited to specified'. In my script I am creating an array of 24 transfer rates for each hour of the day. It works great on SMS 2003 SP3 sites. I can see in the site control file that when I create an address manually with the settings I want, it has the following text in the address, whereas the ones created by my script are missing this.

    BEGIN_PROPERTY_LIST
        <Pulse Mode>
        <0>
        <3>
        <5>
    END_PROPERTY_LIST

Here is the script I am using. It is based on the script provided by Microsoft here: http://technet.microsoft.com/en-us/library/cc180643.aspx

dim rateArray(24)
Dim strSecSiteServer
Dim strSecSiteCode
Dim strSiteServer
Dim strSiteCode
Dim WbemContext
Dim WbemServices
Dim WbemInst
Dim objArgs
Dim lLocator
Dim newep1
Dim newep2
rateArray(0)= 90
rateArray(1)= 90
rateArray(2)= 90
rateArray(3)= 90
rateArray(4)= 90
rateArray(5)= 90
rateArray(6)= 90
rateArray(7)= 90
rateArray(8)= 25
rateArray(9)= 25
rateArray(10)= 25
rateArray(11)= 25
rateArray(12)= 25
rateArray(13)= 25
rateArray(14)= 25
rateArray(15)= 25
rateArray(16)= 25
rateArray(17)= 25
rateArray(18)= 25
rateArray(19)= 25
rateArray(20)= 25
rateArray(21)= 50
rateArray(22)= 90
rateArray(23)= 90
strSiteCode="ABC"
strSiteServer="SCCM01"
Set objArgs = WScript.Arguments
If objArgs.Count < 1 Then WScript.Quit
strSecSiteCode = objArgs(0)
strSecSiteServer = "SERVER" & strSecSiteCode
WScript.Echo strSecSiteCode
Set objArgs = Nothing
Set lLocator = CreateObject("WbemScripting.SWbemLocator")
Set WbemServices = lLocator.ConnectServer(strSiteServer, "root\sms\site_" & strSiteCode)
set WbemContext=CreateObject("WbemScripting.SWbemNamedValueSet")
WbemContext.Add "SessionHandle",WbemServices.ExecMethod("SMS_SiteControlFile","GetSessionHandle").SessionHandle
WbemServices.ExecMethod "SMS_SiteControlFile.Filetype=2,Sitecode=""" & strSiteCode & """", "Refresh", , , WbemContext
'Spawn an SMS_SCI_Address instance
Set WbemInst = WbemServices.Get("SMS_SCI_Address").SpawnInstance_()
wbeminst.AddressType = "MS_LAN"
wbeminst.DesSiteCode = strSecSiteCode
wbeminst.ItemName = strSecSiteCode & "|MS_LAN"
wbeminst.ItemType = "Address"
wbeminst.Order = 1
wbeminst.SiteCode = strSiteCode
wbeminst.UnlimitedRateForAll = 0
wbeminst.RateLimitingSchedule = rateArray
Set newep1 = WbemServices.Get("SMS_EmbeddedProperty").SpawnInstance_()
newep1.PropertyName = "Connection Point"
newep1.Value = 0
newep1.Value1 = strSecSiteServer
newep1.Value2 = "SMS_SITE"
Set newep2 = WbemServices.Get("SMS_EmbeddedProperty").SpawnInstance_()
newep2.PropertyName = "LAN Login"
newep2.Value = 0
wbeminst.Props = Array(newep1, newep2)
wbeminst.Put_ , WbemContext
'comment
WbemServices.ExecMethod "SMS_SiteControlFile.Filetype=1,Sitecode=""" & strSitecode & """", "Commit", , , WbemContext
WbemServices.Get("SMS_SiteControlFile").ReleaseSessionHandle WbemContext.Item("SessionHandle").Value
WScript.Sleep (30000)

Change DP hardware

Fri, 20 Nov 2009 20:02:29 Z

We will switching out 4 of our dp's in the next few months. What are the steps to get the new boxes up and dishing out software? I know I can copy the packages by right-clicking on packages, but how do I handle the the existing dp roles. Do you remove serverA,B,C,D from site systems and then turn off those boxes and then turn on ServerA (new hardware),B,C,D and add the roles back? Anything else to watch out for?

Thanks

machines not installing sccm client

Wed, 18 Nov 2009 13:27:30 Z

several months back, we migrated from SMS to SCCM. We used a client push and an advertisment to get clients upgraded from SMS to SCCM. We have about 3500 users on our fleet. We have one primary and abt 10 secondary sites in different physical locations in the same country. We have enabled the ff client discovery methods : AD System Group Discovery, AD Security Group Discovery, AD System Discovery, Network Discovery and Heartbeat.

The problem is that I have over 700 computers on the console that display "NO" in the client field. I need to investigate why these machines havent installed a client yet. I have no idea where to start, please help.

SQL Reporting services installation

Wed, 25 Nov 2009 09:55:24 Z

I have 2 servers. First have CM Sp2 and SQL 2005 Sp3on Windows 2008. CM have all roles except Reporting Services point.
I wanted to test SQL reporting server on second server because my first server is overloaded. Do I need also install there another SQL instance or just RS? Also I have created domain account for Reporting service. What else should I keep in mind doing this?

Thanks

Logging into machine slow after installing SCCM 2007 client

Mon, 15 Dec 2008 15:57:33 Z

I have been working on the problem for weeks now and have not found anything.

I installed the SCCM 2007 client on several hundred of our lab machines. The worked fine for about 2-4 weeks, I cannot pinpoint when they started slowing down. But, it finally got to the point where it would take a user like 2-5 minutes to log into a machine. I finally ended up having to uninstall the client from these machines. Once the client was installed, log on times returned to normal.

The clients were installed in mixed mode. This is the only way I will be able to install the client in our current AD configuration. All these machines were running the latest patched SP3 version of Windows XP Pro.

I had this problem also back in June or so and had to uninstall the clients. Anyone experience this type of problem?

Melvin Stevens

Melvin Stevens

Deinstall WAIK 1.1 when upgrading from SP1 to SP2

Wed, 25 Nov 2009 12:29:04 Z

Hi,

In the following document (http://technet.microsoft.com/en-us/library/ee344146.aspx) I read this:

"Windows Automated Installation Kit (Windows AIK) Requirements
Operating System Deployment in Configuration Manager 2007 SP2 requires the Windows 7 Windows Automated Installation Kit 2.0 release (version 6.1.7600).

The Windows AIK (version 1.0 for Configuration Manager 2007 or version 1.1 for Configuration Manager 2007 SP1) must be uninstalled from the SMS Provider computer and the computer must be restarted before beginning the upgrade process. When the site is upgraded to SP2, the Windows AIK 2.0 will be installed on the SMS Provider computer."

Does this mean that I manually have to uninstall WAIK 1.1 before upgrading to SP2? I thought this was handled automatically by the SP2 installation.

/Fredrik

Hotfixes necessary for running SCCM 2007 R2 SP2 on SQL 2008 Standard?

Wed, 25 Nov 2009 12:51:55 Z

Hi,

I have read several posts in the forum on the subject SQL 2008 and SCCM 2007 R2 SP2 and what hotfixes that should be applied for this solution. For me it's not yet crystal clear exactly what hotfixes that are necessary. Is there an official document from Microsoft that states what hotfixes to download?

Multiple servers across domain's / networks & SCCM 2007 setup

Tue, 24 Nov 2009 11:42:06 Z

I Have approx 50 sites that we support, each with there own seperate domain - in effect they are there own network, so approx 50 servers and say upto 2000 pc's. We have remote access and connections from our headoffice to all sites and we are looking at implementing a SCCM 2007 server to manage these sites with regards to auditing and software deployment etc. When the MP is setup on the primary site(my server in office) what would be the process of getting this deployed out to the sites, would it be a case of installing secondary sites on the servers out there and then deploying client to workstations through local GPO? Am relatively new to this product, so am currently in the testing and breaking stage! :) I'm just trying to iron out the issues i am having with my server and local lan test enviroment i have setup. Thanks for any help, just tell me i'f i'm asking stupid questions! :) Mike.

SMS_MP_CONTROL_MANAGER Failed to create the CCM_Incoming Virtual Directory

Wed, 25 Nov 2009 02:23:37 Z

Hello -

I'm hoping someone could help me with this problem. I've searched so many websites trying to resolve this issue and it seems no matter what I try I keep getting the same error message.

I've followed the steps in setting up SCCM 07 from this web site which was very nicely done! I've also followed the directions on Microsofts Tech Net website on how to configure WebDav and IIS settings.

I'm working on a Virtual Windows Server 2008 32-bit OS, SP2, SCCM 07 SP2, IIS7

Here is the message I get in the log files:

----------------------------------------------------------------------------------------------------------------------------
Message ID: 4963
Process ID: 4364
Thread ID: 7996

Componet: SMS_MP_CONTROL_MANAGER

MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.

Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.

Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.

Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
-------------------------------------------------------------------------------------------------------------------------------

I could be completely wrong but I read somewhere that with the latest version of IIS doesn't install these user accounts. I checked to see if those accounts existed and they didn't.

I've tried what this one website mentioned:

http://myitforum.com...-directory.aspx

- Remove the MP role from the Site Server. Watch the MPSetup.log to ensure that the removal is complete.
- Uninstall the IIS component from the OS of the Site Server.
- Reboot the Site Server.
- Run ccmdelcert.exe from the SMS Toolkit.
- Reinstall the IIS component (with BITS) on the OS of the Site Server.
- Go into the IIS manager and allow WebDav.
- Add the MP role to the Site Server. Watch the MPSetup.log to ensure that the installation completes correctly.

These steps didn't seem to work, probably because it was for SMS 2003.

Here is the MPmsi log file:

<11-24-2009 17:39:28> SMSMP Setup Started....
<11-24-2009 17:39:28> Parameters: C:\PROGRA~1\MICROS~3\bin\i386\ROLESE~1.EXE /install /siteserver:DELGADO SMSMP
<11-24-2009 17:39:28> Installing Pre Reqs for SMSMP
<11-24-2009 17:39:28> ======== Installing Pre Reqs for Role SMSMP ========
<11-24-2009 17:39:28> Found 1 Pre Reqs for Role SMSMP
<11-24-2009 17:39:28> Pre Req MSXML60 found.
<11-24-2009 17:39:28> No versions of MSXML60 are installed. Would install new MSXML60.
<11-24-2009 17:39:28> Enabling MSI logging. msxml6.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6MSI.log
<11-24-2009 17:39:28> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\00000409\msxml6.msi
<11-24-2009 17:39:30> msxml6.msi exited with return code: 0
<11-24-2009 17:39:30> msxml6.msi Installation was successful.
<11-24-2009 17:39:30> ======== Completed Installion of Pre Reqs for Role SMSMP ========
<11-24-2009 17:39:30> Installing the SMSMP
<11-24-2009 17:39:30> Passed OS version check.
<11-24-2009 17:39:30> IIS Service is installed.
<11-24-2009 17:39:30> checking WebDAV configuraitons
<11-24-2009 17:39:30> WebDAV is configured
<11-24-2009 17:39:30> No versions of SMSMP are installed. Installing new SMSMP.
<11-24-2009 17:39:30> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<11-24-2009 17:39:30> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<11-24-2009 17:40:24> mp.msi exited with return code: 1603
<11-24-2009 17:40:24> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<11-24-2009 17:40:24> Fatal MSI Error - mp.msi could not be installed.

Component Services (DCOMCNFG) is running properly, no error messages when I was browsing around.

Any advice would be greatly appricated!

Thanks!

Any best practices regarding naming standards for site codes?

Tue, 24 Nov 2009 14:23:34 Z

Hi,

Short question. Are there any best practices regarding namning standards for site codes? We are currently in the process of setting up an SCCM hosting environment for multiple customers. One option is to go with XX1, XX2 and so on for every new site in a hierarchy. But is that the most flexible solution for a certain hierarchy?

Input from anyone else with the same experience would be interesting.

Regards,
Fredrik

Secodnary site console

Fri, 20 Nov 2009 11:00:05 Z

Hi all,

I'm trying to configure a secondary site on our sccm native mode infrastructure. THe secodnary site installation is OK, but i cannot access it via the console. I get the message :
The Site Server cannot be contacted or trying to connect to an incompatible Site Server version. Please enter a new Site Server Name. and above "invalid namespace".

I've tried to reinstall it but it's all the same.

I've checked wmi and it's ok, though the "root/sms" is missing

How can i solve this ?

Thanks,

Nicolas

Migration of SCCM and reassignment of clients

Wed, 21 Oct 2009 06:39:01 Z

Hi,

I have a few questions about the migration process for SCCM.

Lets say we have site X (old SCCM ) and site Y (new SCCM). Site Y will be a fresh install of SCCM. Package/drivers etc will be copied to the new SCCM-server. When we decide to point the clients to the new site, what actions should be done?

I know that I neew to deactive site boundaries on the old SCCM server and activate them on the new one. Then I assume the clients will reassign themselves? Is that really it or is there anything else that I should do that I haven't thought about?

Regards,
Fredrik

Client Push Fails "Failed to correctly receive a WEBDAV HTTP request" SCCM 2007 Mixed Mode

Fri, 14 Dec 2007 14:56:19 Z

Hey guys, I am having client push issues from the server. It fails with the following two error messages: "Failed to correctly receive a WEBDAV HTTP request." "Failed to successfully complete HTTP request." I can install the client manually if i point it to the server through command line and use the "/service" switch and it will talk back to the server and show up as Client = Yes Approved and Active.

I am assuming its a permission issue, but the account I am using to push the client is an administrator on both the server and the client PC's.

Any help is greatly appreciated.

P.S. If the Site Status is showing OK, why is it "Offline". I don't see any errors in any of the logs.

Thank you,

Drew

==========[ ccmsetup started in process 2836 ]========== ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Version: 4.0.5931.0000 ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
CCMHTTPPORT:    80 ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
CCMHTTPSPORT:    443 ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
CCMHTTPSSTATE:    0 ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
CCMHTTPSCERTNAME:    ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
FSP:    BA-NET-030.AD.UFL.EDU ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
CCMFIRSTCERT:    0 ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Config file:      C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Retry time:       10 minute(s) ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
MSI log file:     ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
MSI properties:    INSTALL="ALL" SMSSITECODE="OFA" SMSSLP="ba-net-046.ad.ufl.edu" CCMLOGLEVEL="0" SMSMP="ba-net-046.ad.ufl.edu" SMSSLP="ba-net-046.ad.ufl.edu" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="BA-NET-030.AD.UFL.EDU" CCMFIRSTCERT="0" ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Source List: ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
                  \\ba-net-046.ad.ufl.edu\SMSClient ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
                  \\BA-NET-046\SMSClient ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
MPs: ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
                  ba-net-046.ad.ufl.edu ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
Sending Fallback Status Point message, STATEID='100'. ccmsetup 12/14/2007 9:39:38 AM 592 (0x0250)
State message with TopicType 800 and TopicId {8D7DCE69-73F6-432E-8AB4-A92D3645084D} has been sent to the FSP FSPStateMessage 12/14/2007 9:39:39 AM 592 (0x0250)
Running as user "SYSTEM" ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Detected 9913 MB free disk space on system drive. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Client OS is not Windows XP Embedded ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Successfully ran BITS check. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Select first cert flag is set, choosing the first certificate valid for ConfigMgr usage. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Successfully loaded ccmsetup manifest file. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Failed to correctly receive a WEBDAV HTTP request. ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401) ccmsetup 12/14/2007 9:39:39 AM 2292 (0x08F4)
Sending Fallback Status Point message, STATEID='301'. ccmsetup 12/14/2007 9:39:39 AM 592 (0x0250)
State message with TopicType 800 and TopicId {30BD41FF-0902-4BB8-AEFC-7781E6C1A409} has been sent to the FSP FSPStateMessage 12/14/2007 9:39:39 AM 592 (0x0250)

Problem after applying SCCM SP2

Sat, 24 Oct 2009 12:29:58 Z

I installed SCCM SP2. The installation appeared to complete normally. A review today of my site status reveals a critical status for the SMS_MPCONTROL_MANAGER component. Reviewing the messages for that component reveals errors stating "MP Control Manager detected management point is not resonding to HTTP requests. The HTTP status code and text is 500, Internal Server Error".

Has anyone else installed SP2 and had these problems? Any recommendations from the SCCM guru's on how to recover? Any and all assistance is appreciated.

Installing SCCM Client in multiple-MP environment

Fri, 20 Nov 2009 19:00:46 Z

I'm hoping someone has already figured this out.

We need to deploy SCCM clients to workstations via logon script in a multiple MP environment (5 primary sites, 50+ secondary sites). The consensus seems to be to include the following line in the logon script:

ccmsetup /MP:<MPservername> SMSSITECODE=<sitecode> FSP=<FSPservername>

We will wrap this in a VB script, of which I've found several examples. But has anyone written or seen a script that will interrogate AD to identify the appropriate sitecode and servernames based on IP address (or AD site)? We don't want to write 5 (or 50) versions of the script, just one that is dynamic. All of the secondary sites will be (proxy) MPs and FSPs, so we'd want to pull the remaining client binaries (beyond ccmsetup.exe itself) from the closest SCCM server, i.e. the /MP. (A secondary configured as a proxy MP will work in this regard, have tested that.)

TIA,
Jeff Kantner

ccmallowsilentreboot parameter not working then installing on Windows 2000 Sp4

Sun, 22 Nov 2009 20:57:16 Z

Hi

I have alot of Windows 2000 servers, where I am deploying SCCM Sp2. I have specified the CCMALLOWSILENTREBOOT=1 in the client push parameters.

When I push the agent from the SCCM console to Windows 2000 servers, the installation updates the BITS on the clients and then waits for manually reboots of the server s why ?

I though when the CCMallow... parameter was specified then reboots was also executed on the BITS installations.

When I look in the ccmsetup.log file, I can see that the BITS is installed with "/Norestart", and after the BITS is installed, I only get a "installation will continue after restart" or something like that..

How do I force reboots, also when BITS is updated ?

Client Deployment Failure Report - Stale records

Thu, 23 Oct 2008 15:32:11 Z

I know this has been asked and answered in January, but I'd like to verify the information still holds true... In our environment we use the Client Deployment Failure Report to regularly check on our automated GPO rollout of the ConfigMgr client as systems are built and joined to the domain. Unfortunately, we have a fair number of machines that get built up for testing (typically VMs) and then are permanently destroyed. I get a lot of client installation failures due to the fact the system was shut down or restarted during the ConfigMgr client install. The GPO deploying ccmsetup.msi does not run again (I assume because it technically succeeded installing the bootstrap), and the test machine lands on this report.

Typically these dev VMs are built and destroyed before the failure can be addressed, so they become a permanent fixture on this report. In the following thread Wally confirms what we've seen, that a successful install clears this machine from the report. But if there's never a success, these machines are permanently stuck on this report. Our report is littered with these machines all the way back to our original site installation, which really detracts from the value of the report.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2740782&SiteID=17

Is there a mechanism yet for cleaning this report up? If not, can someone point me toward documentation on how I might request this functionality in a future SP? Or if it makes more sense to funnel this through our TAM, I can do that too.

Appreciate your feedback. Thanks.

Questions about implementing a Branch Distribution Point

Tue, 24 Nov 2009 18:40:59 Z

Currently, my only boundary is an Active Directory Site. If want to create a protected BDP for one of my offices do I just create a boundary for the IP address range of that office? Will that suffice, or do I have to delete the AD Site boundary and create new boundaries? i.e., will the IP Range boundary override the AD Site boundary?

How long after I install a BDP will the client start pulling packages from it?
Is there something I can do on the client to force it to recognize the new BDP faster?
How do I tell if a client is ready to use the new BDP?
How do I tell if the package is pulled from the BDP? What log file? What should I look for in the log file?
What happens if the package is not on the BDP?

SCCM Hotfixes and availability on WSUS

Sat, 14 Nov 2009 10:29:58 Z

Hi,

Does anyone know if MS have plans to add all the SCCM hotfixes to the WSUS environment so we can scan our servers for possible hotfixes to install?

Regards

Mike

SCCM client vs. Windows Firewall- can't see WMI on the exceptions list?

Tue, 24 Nov 2009 14:48:29 Z

I have some Windows XP SP2 clients that I am trying to install the SCCM client on. Windows Firewall is turned on, I can't disable it (company policy)... I have read the document on creating exceptions in Windows Firewall to permit the SCCM client to work. I see that I am supposed to create a firewall exception for WMI, but when I open Firewall and go to the Exceptions tab, WMI is not listed.

Is there another way to create the WMI exception? Or is there a way for me to add WMI to the list of Exceptions in firewall?

Thanks!
-Janet

monitoring sites upgrade to service pack 2

Tue, 24 Nov 2009 11:50:23 Z

Hi everybody,

pls is there any log file where informations about an upgrade process are stored?
I am upgrading secondary site that is connected via very slow WAN and I see a status UPGRADE in ConfigMgr for 2 days now.
Is it possible to see downloading progress and installation progress somewhere?

Thank you for all replies

MCP,MCTS | jan-marek.com

Issue manually installing clients in SCCM 2007 R2....

Mon, 23 Nov 2009 12:42:15 Z

Hi everyone, after some help if you would be so kind.

I have to admit i'm new to SCCM 2007, i've just deployed a WSUS 3.0 sp2 server which is working as it should and sychronising with clients etc but i have the requirment for some features of SCCM 2007 - but it's giving me a bit of a headache! :)

I have an issue installing clients for SCCM 2007, it doesnt seem to work and reports error: [Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)]LOG]!><time="12:25:03.578+000" date="11-23-2009" component="ccmsetup" context="" type="3" thread="2300" file="ccmsetup.cpp:5808"> In the log file. Have checked on the client and the CCMsetup service does appear but seems to start, then stop and nothing showins in control panel.

My server setup is:

Windows server 2008 R2 Enterprise
SCCM 2007 R2 - Mixed mode
WSUS 3.0 SP2

I know it's not ideal for SCCM 2007 & WSUS to co-habit a box, but for testing and scaleability thats what i've got.

With regards to the client install i probably ideally need to do a manual install as i have some pc's that are outside of the domain in a workgroup setup, i also have multiple sites in there own domain which need to be added in.

Hope that kind of make sense, thanks for your time and as i say any help much appreciated.

Cheers, Mike.

**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER

Sun, 22 Nov 2009 08:33:25 Z

Hi Guys

We just reinstall a secondary site using different site code after uninstalling and removing all its previous instances. After reinstallation, We created distribution point as \\secsite\packages$ and removed default distribution point as of server itself \\secsite but it is still showing just one distribution point as \\secsite. We created Management Point but it is missing mpcontrol.log file.

MPFDM.log on that secondary site reported as below:

Verifying local MP outbox directory D:\SCCM\MP\OUTBOXES\amtproxy.box for SMS_AMT_PROXY_COMPONENT exists... SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:43:08 PM 7852 (0x1EAC)
**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:43:08 PM 7852 (0x1EAC)
Worker thread [SMS_AMT_PROXY_COMPONENT] cannot update environment so skiping outbox processing. SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:43:08 PM 7852 (0x1EAC)
Updating environment... SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:43:08 PM 10072 (0x2758)
Verifying local MP outbox directory D:\SCCM\MP\OUTBOXES\AIKbMgr.box for Asset Intelligence KB Manager exists... SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:43:08 PM 10072 (0x2758)
**ERROR: Cannot find path for destination inbox Asset Intelligence KB Manager on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:43:08 PM 10072 (0x2758)
Worker thread [Asset Intelligence KB Manager] cannot update environment so skiping outbox processing. SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:43:08 PM 10072 (0x2758)
Updating environment... SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:44:08 PM 7852 (0x1EAC)
Verifying local MP outbox directory D:\SCCM\MP\OUTBOXES\amtproxy.box for SMS_AMT_PROXY_COMPONENT exists... SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:44:08 PM 7852 (0x1EAC)
**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER 22/11/2009 5:44:08 PM 7852 (0x1EAC)

I did bit googling and followed exact instructions as per couple of threads below but issue is still there

http://myitforum.com/cs2/blogs/scassells/archive/2009/07/20/error-cannot-find-path-for-destination-inbox-sms-amt-proxy-component-on-server-registry.aspx

}

http://social.technet.microsoft.com/forums/en-US/configmgrsetup/thread/c4d26074-0c5a-40e8-ab94-c3ebd7ba3055/

Please advice

Thanks

Server Engineer

sccm client install issue (uninstall and reinstall)

Mon, 23 Nov 2009 16:55:51 Z

We have sccm 2007 installed and running. I am trying to roll out the client, and i have done a push install to a large batch of client computers. Inside the console, some of the computers state they have the client, some state they do not. On the computerts that state they do not have the client, if I go to them, I can see the ccm proccess running. If I try to do a push to the client again, using the "Always install (repair or upgrade existing client)" option, the console still says it doesn't see the client installed (which it actually is). BUT, if I go to the client, do a manual ccmsetup.exe /uninstall, and *them* reinstall the client, the installed client shows up in the console.

What I want to know is, is there an easy way to get the console to see the client where I don't have to manuall uninstall the client from each individual computer.

Setup unable to create directory CCM_Incoming. Error 800cc801

Fri, 20 Nov 2009 10:22:17 Z

I am getting this error when trying to install the MP in my ConfigMgr 2007 R2. I've seen some suggestions of reinstalling IIS. I do NOT want to do that. The last time I saw this error, I spent DAYS with MS support trying to resolve it, at which point, being frustrated and fed up with the time and failure to resolve the issue, I reinstalled the server completely, and the installation then succeeded. I'm not sure how it broke, I believe when I tried to update to R2.

Server 2008 SP2 x86, WSUS 3.01 SP2. IIS, webdav configured properly, etc. Nothing else installed on the server.

Any help would be greatly appreciated!

Getting the Installation Date of the SCCM Clients out of SCCM reports

Sat, 21 Nov 2009 17:47:21 Z

can any one help me to get list of new sccm clients installed during particular duration say "last 30 days"

also i would like to have in last month what are new softwares included in to the site using asset intelg.

thanks
Shajahan

FYI: Configmgr SP2 (RTM) release notes and KB960037 on Windows Server 2008 x64 (SP2)

Sat, 21 Nov 2009 05:14:28 Z

This isn't a question... just an FYI

Windows Server 2008 Service Pack 2 supercedes the KB960037 notation in the Configmgr SP2 release notes applied to Windows Server 2008 x64.

You'll get an "The update does not apply to your system" if you try to apply the KB960037 on Windows Server 2008 SP2 (x64)

Configmgr SP2 release notes state that KB960037 needs to be installed prior to upgrading Config Manager 2007 to SP2 on Windows Server 2008 x64.

A call to Microsoft Tech Support confirmed that Windows Server 2008 Service Pack 2 superceded this requirement.

If you've already applied Windows Server 2008 Service Pack 2 to your x64-based Windows Server 2008 install, you can safely disregard the KB960037 work-around in the first gotcha of the RELNOTES.

(the only KB960037 downloads are server03 and Vista... the Vista fix applies to server08 ... but not if already server08SP2... the message read (pronounced: red): "The update does not apply to your system")

And yes, after confirming the obsolescence of KB960037, I proceeded into a very successful ConfigMgr SP2 upgrade.

Snakeman

Couple of SCCM Questions

Fri, 20 Nov 2009 19:29:34 Z

I was at a client a few days ago and they had a few questions I couldn't answer and was looking for some help on them.

1. Will a client, who has an advertisment downloaded to its cache, run the advertisment when the machine is not on the network?
2. Can SCCM check versions of files before an advertisment is run?

Thanks!

Client install through update point

Thu, 19 Nov 2009 17:29:51 Z

I have been reading through and not found enough to get this working. I will start with that other than 10PM to 4AM when no one is here the system have deepfreese installed and enabled so any changes revert so a push is not really an option. I have a WSUS server up and running on a server 2008 64 box and every one is pointed to it and getting their updates. I installed SCCM on the same box and it is up and running, it has all of the systems in the collections and no errors in the logs. I setup a maintance window for 10:30PM-3:30AM and a wakup for 9:00 so everything will be online. I enabled Software Update Point Client Installation, and had it get the newest version, but I do not see anything new in WSUS (I do not have auto approval on) and none of the clients had the client install last night. What is my next step?

Failed to correctly receive a WEBDAV HTTP request. Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 200)

Fri, 27 Feb 2009 13:57:17 Z

i trie to install many clients with any forms ands all failes.

this is the log.

clinets are xp and vista
server is w2k3 r2 sp2
sccm 2007 sp1 r2

==========[ ccmsetup started in process 3104 ]========== ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Version: 4.0.6221.1000 ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
CCMHTTPPORT:    80 ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
CCMHTTPSPORT:    443 ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
CCMHTTPSSTATE:    0 ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
CCMHTTPSCERTNAME:    ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
FSP:    ESMADVSEM06.mydomain.COM ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
CCMFIRSTCERT:    0 ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Config file:      C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Retry time:       10 minute(s) ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
MSI log file:     ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
MSI properties:    INSTALL="ALL" SMSSITECODE="ES2" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="ESMADVSEM06.mydomain.COM" CCMFIRSTCERT="0" ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Source List: ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
                  \\esmadvsem06.emydomain.COM\SMSClient ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
                  \\ESMADVSEM06\SMSClient ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
MPs: ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
                  esmadvsem06.mydomain.COM ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
Sending Fallback Status Point message, STATEID='100'. ccmsetup 27/02/2009 10:45:34 3792 (0x0ED0)
State message with TopicType 800 and TopicId {356104FE-9C4B-45D4-8E43-8F30A6BC85D1} has been sent to the FSP FSPStateMessage 27/02/2009 10:45:35 3792 (0x0ED0)
Running as user "SYSTEM" ccmsetup 27/02/2009 10:45:35 3320 (0x0CF8)
Detected 54918 MB free disk space on system drive. ccmsetup 27/02/2009 10:45:35 3320 (0x0CF8)
DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 27/02/2009 10:45:35 3320 (0x0CF8)
Client OS is not Windows XP Embedded ccmsetup 27/02/2009 10:45:35 3320 (0x0CF8)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 27/02/2009 10:45:35 3320 (0x0CF8)
Successfully ran BITS check. ccmsetup 27/02/2009 10:45:36 3320 (0x0CF8)
SSL State is invalid: 0x80000000. ccmsetup 27/02/2009 10:45:36 3320 (0x0CF8)
SSL Registry Value HttpsState is corrupt. Assuming Client SSL is disabled. ccmsetup 27/02/2009 10:45:36 3320 (0x0CF8)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 27/02/2009 10:45:36 3320 (0x0CF8)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 27/02/2009 10:45:36 3320 (0x0CF8)
Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed. ccmsetup 27/02/2009 10:45:36 3320 (0x0CF8)
Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab. ccmsetup 27/02/2009 10:45:37 3320 (0x0CF8)
Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml ccmsetup 27/02/2009 10:45:37 3320 (0x0CF8)
Successfully loaded ccmsetup manifest file. ccmsetup 27/02/2009 10:45:37 3320 (0x0CF8)
Failed to correctly receive a WEBDAV HTTP request. ccmsetup 27/02/2009 10:45:37 3320 (0x0CF8)
Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 200) ccmsetup 27/02/2009 10:45:37 3320 (0x0CF8)
Sending Fallback Status Point message, STATEID='301'. ccmsetup 27/02/2009 10:45:37 3792 (0x0ED0)
State message with TopicType 800 and TopicId {5F99FFAE-A88C-45C7-A45C-DA0D575DDBCA} has been sent to the FSP FSPStateMessage 27/02/2009 10:45:37 3792 (0x0ED0)

Unknown Site Mode & Connection Type

Wed, 18 Nov 2009 20:21:12 Z

Greetings All,

I am having an annoying issue with clients getting the “Site Mode” and “ConfigMgr Connection Type” in the system properties on client. Here is some back ground info to help see how my current setup is:

-Jan of 09 got SMS 2007 installed and extended AD before install. The ExtASSch log shows no signs of errors. SMS 2003 was installed 2 years ago so some of the attributes where already in AD but that log successfully updated the class and schema. I manually created the “Systems Management” container in AD and gave the “SCCM Servers” group full access to that container. (The SCCM Servers group has the SCCM Server Computer account in it from AD, thought to use a group rather then apply a computer account to the container) The “SMS-MP” and “SMS-SLP” folders are there and the “SMS-Site-Sitecode” record is there as well. Publish this site in AD, publish the default MP in DNS and require secure key exchange between sites are all checked. I found the SRV record in DNS and is correct. We have 2 DCs and both are a GC. My boundary is a AD Site type and this is the only domain in the forest. Site is Mixed Mode. GC port is open on the DC fw.

-April of 09 I installed SP1 and have been using SCCM for app deployment successfully since January and throughout the summer as well.

-The problem started after the middle of September when I installed R2 on top of SP1. I wanted to use the “Unknown Client” feature with R2 but in order to do so they wanted to change some options on my site. In the site properties, on the site mode tab, they wanted to me to uncheck “this site contains only ConfigMgr 2007 Clients”, set the approval settings to “manually approve each computer” which I did. Had to install the PXE role and add a bunch of boot images and OS images to the OSD container. After much deliberation trying to get the OSD to work I gave up using SCCM for OSD and made a WDS server on a separate server instead.

- I had changed all the settings back to the norm after trying unknown OSD and everything seemed to be ok but this is when the problem started. About a week after I upgraded a bunch of computers to Vista (End of September). These upgrades were used with a Vista Enterprise CD and when going through the installation I would format the computer then hit install (to create a new GUID). When I joined the computer to the domain the client would get the SCCM Client and show up in the “All Systems” container in SCCM but I couldn’t approve it because the client approval wasn’t complete since the client couldn’t get the Site Mode and Connection Type. When I installed all of these machines the SMS_Client_Config_Man component was giving me 2 major errors one about not being able to create a new DDR for the client because it couldn’t read critical properties on the client, and another for some computer that are not connected to the network trying to install the client. Since then I had fixed the issue of the DDRs and the component it giving me no errors.

-In October I installed SP2 on the server for Windows 7 support and the new client version.

- I know since my AD is extended I don’t have to use a SLP and WINs is not needed, but the SLP role is installed on my SCCM server. The After doing some more research my LocationService log from a client machine looks like this:

<![LOG[Sending Fallback Status Point message, STATEID='500'.]LOG]!><time="10:34:18.174+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="fspclientdeployassign.cpp:49">

<![LOG[Processing pending site assignment.]LOG]!><time="10:34:18.378+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="lsad.cpp:3328">

<![LOG[Assigning to site 'CDR;']LOG]!><time="10:34:18.379+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="lsad.cpp:3334">

<![LOG[LSVerifySiteVersion : Verifying Site Version for <CDR;>]LOG]!><time="10:34:18.379+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="lsad.cpp:5321">

<![LOG[LSGetSiteVersionFromAD : Failed to retrieve version for the site 'CDR;' (0x80004005)]LOG]!><time="10:34:18.501+360" date="11-18-2009" component="LocationServices" context="" type="3" thread="4204" file="lsad.cpp:5123">

<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="10:34:18.502+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="lsad.cpp:2261">

<![LOG[Retrieved SLPs from AD]LOG]!><time="10:34:18.598+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="lsad.cpp:2265">

<![LOG[Raising event:

instance of CCM_CcmHttp_Status

{

DateTime = "20091118163418.612000+000";

HostName = "XXXXXXXXXXXXXXX";

HRESULT = "0x00000000";

ProcessID = 2488;

StatusCode = 0;

ThreadID = 4204;

};

]LOG]!><time="10:34:18.612+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="event.cpp:525">

<![LOG[LSGetSiteVersionFromSLP : No site version returned from SLP for site <CDR;>]LOG]!><time="10:34:18.615+360" date="11-18-2009" component="LocationServices" context="" type="3" thread="4204" file="lsad.cpp:5284">

<![LOG[LSVerifySiteVersion: Failed to get Site Version from AD and SLP]LOG]!><time="10:34:18.615+360" date="11-18-2009" component="LocationServices" context="" type="3" thread="4204" file="lsad.cpp:5398">

<![LOG[Sending Fallback Status Point message, STATEID='608'.]LOG]!><time="10:34:18.616+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="fspclientdeployassign.cpp:49">

<![LOG[Won't send client assignment fallback status point message because last assignment message was sent too recently.]LOG]!><time="10:44:18.221+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="fspclientdeployassign.cpp:184">

<![LOG[Processing pending site assignment.]LOG]!><time="10:44:18.222+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="lsad.cpp:3328">

<![LOG[Assigning to site 'CDR;']LOG]!><time="10:44:18.222+360" date="11-18-2009" component="LocationServices" context="" type="1" thread="4204" file="lsad.cpp:3334">

The ClientIDManagerStartup log looks like this:

<![LOG[RegTask: Failed to refresh site code. Error: 0x80004005]LOG]!><time="13:34:27.426+360" date="11-18-2009" component="ClientIDManagerStartup" context="" type="3" thread="4204" file="regtask.cpp:172">

<![LOG[RegTask: Initial backoff interval: 1 minutes]LOG]!><time="13:34:47.427+360" date="11-18-2009" component="ClientIDManagerStartup" context="" type="1" thread="4204" file="regtask.cpp:1830">

<![LOG[RegTask: Reset backoff interval: 257 minutes]LOG]!><time="13:34:47.427+360" date="11-18-2009" component="ClientIDManagerStartup" context="" type="1" thread="4204" file="regtask.cpp:1831">

<![LOG[Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt.]LOG]!><time="13:34:47.427+360" date="11-18-2009" component="ClientIDManagerStartup" context="" type="1" thread="4204" file="regtask.cpp:146">

-If I log in to a client machine with this error and manually discover the site code it works with no problem.

-Version 400.6487.2000 is published to the site. (SCCM 2007 SP2 R2)

Sorry for the post being so long. I wanted to give as much info as possible to help eliminate possible issues. Looking through an endless amount of forums posts and trying a few different things haven’t helped yet.

Thanks Everyone.

Can I find out who requested the push installation to specific clients?

Fri, 20 Nov 2009 13:44:01 Z

We are planning to deploy SCCM 2007 R2, but we are still waiting for approval from works council. Now, one of the 6 SCCM admins must have started client push installation for all clients - likely he chose "All Systems" collection and hit "Install Client".

Is there a way to find out who did that? From logs or database?

SP2 BUG??? Removing a Site role removes the ConfigMgr Component Server and SMS Executive services as well

Fri, 20 Nov 2009 11:49:34 Z

Hi All,

I have a newly build SCCM 2007 R2 + SP2 environment and I am in the process of migrating Branch Distributions Points from a legacy SCCM 2007 environment to the new one. I have had the typical PXE Service Point issues along the way and, as usual, I have been removing and re-assigning this role. Apart from two centraiised servers all of my other branch servers are BDPs and PSPs. In this scenario the site system shows four components:

1) Site System
2) ConfigMgr Component server
3) Distribution Point
4) PXE Service Point

If I remove the PSP role the Site System automatically removes the PSP, BUT, also removes the ConfigMgr Component Server as well. Under Site Status I can see the BDP server, however, under Component Status the entire servers component list disappears. I have done this same operation many times prior to SP2 with no trouble! Another symptom is that the "SMS EXECUTIVE" service is removed from the BDP. I have noticed, however, that any software, OS/boot, driver package distribution point status stays in place.

This is very weird and disconcerting to see in the console!

Can any one else with SP2 confirm this behaviour??

Thanks,

Nathan

NSutton