I have two domains: abc.test.com and xyz.test.com. In the field abc.test.com there a central site and two child primary sites. Customers need to manage the site xyz.test.com. I created a child primary site domain xyz.test.com console but the central site it does not appear. The ad schema is extended to the forest but the central site does not display the System Management container xyz.test.com domain.

The child primary site is not recognized by the central site and not receive the packages.

Windows Server 2008

SCCM 2007

We have several hundred workstation BDP's that are currently XP, and our agency needs them all upgraded to Win7.  Was wondering if anyone has gone through this, and has some ideas for doing them remotely, rather than having to bring each back to home site to OSD, or, bring one out to replace the existing one (most of our sites don't have spares with large hard drives)?

I had thought of temporarily making a reqular workstation at the remote site a BDP, getting the OSD packages to it, OSDing the original BDP, then reset it back up.

From what I understand, there is no way to keep client, packages, or it being a site system, and it must be first removed, then afterwards replaced in the site server's DB?

Thanks.

Hi

I have installed sccm 2007 client in a client machine. ccmsetup log shown successful installation with no error. But in control panel applet does not have any policy yet. Again in sccm console client status is 'no'.

client log file:

ccmexec has got error:

1. error loading service setting

2. phase 0 initialization failed

3. service initialization failed

other client log is fine.

can anyone please help diagnosis this client installation issue. I have reinstalled it by repairing WMI, deleting certificate.

I have found many documents on installing Configuration Manager on a Windows 2008 R2 server, they all say the same thing, insert Windows CD and chose from the menu, our ISO does not have that option, it only has one button on the splash screen, "Install Now", I have not been able to find alternate ways of installing this, can anyone assist, as it is a prerequisite for Forefront, and we are trying to start marketing Forefront with our server packages.  Thanks in advance for any advice or assistance. 

Osyrys

We have the SCCM client installed on all our production servers and this was installed using the client push installation method.  Although we have 6 servers in our testing environment that mistakenly had the client installed previously.

We have removed the client from these servers using the ccmsetup.exe /uninstall command and this has successfully uninstalled the client, however the 6 servers are still showing in the Servers collection of the console with a client status of "Yes"

We have updated the collection membership and refreshed the collection many times after removing the client, although it still appears as the servers have the client installed even though they do not.  Do we need to manually delete the server from the collection (query based) and then let SCCM rediscover them through the next system discovery cycle???

Many thanks

Pamela.

I noticed YELLOW mark in System status(snap attached) . Everything working well now,so why it is ?

SCCM 2007 sp2

Suddhaman

Paul.

Hello,

I have a problem only on 1 server :

Site Primary (Parent Domain) --> Mode : Push Install --> On Server Domain Control (Child Domain).
In the ccmsetup.log, I have :

MSI: Failed to start serviceSMS AgentHost(CcmExec).Verify that youhave sufficient privilegesto start systemservices.
Installation failed with error code 1603

Nota : I logged on Configuration Manager COnsol with admin domain (Parent Domain).

F.

When the SCCM server attempts to connect to the admin$ share of a Windows XP computer, it gives the following errors:

 NetServerGetInfo failed (1726)

Failed to determine whether or not the target machine is a DC (1726)

And then the installation attempt goes into retry mode.  The account that we use to connect to the admin$ share is in the local admin group of the client's computer.  Any ideas?

I'm moving my SCCM site servers from Server 2003 32 bit to Server 2008 64 bit.

I've successfully installed SQL 2005 64 and WSUS 64 and SCCM 2007 SP2 but the prerequisite for R3 just won't install.

I'm running it from a command prompt with elevated permissions and generating a log file. The current version is: 4.00.6487.2000

msiexec.exe /I SCCM2007-SP2-KB977384-ENU.msi /L*v c:\KB891073-X86.log

MSI (c) (10:0C) [19:20:09:996]: Windows Installer installed the product. Product Name: Software Update for ConfigMgr 2007 SP2 (KB977384). Product Version: 4.0.6487.2157. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

Property(S): SmsIncorrectLang = This hotfix does not match the installed language version of Configuration Manager 2007

Property(S): SmsIncorrectVersion = This hotfix is not valid for this version of Configuration Manager 2007

I've successfully installed this in my lab. I don't see how I could have the wrong version.

Property(S): SmsConnectDatabaseFail = Cannot connect to database server : [InstSMSDatabaseServer], database name : [InstSMSDatabaseName]

This is and English install of SCCM.

I've tried installing client on the server, extracted the msi file to an msp which I successfully installed. But R3 still wants Kb977384 before it will install.

Any help would be greatly

appreciated.

.

hi,

i'm trying to capture an image from a system in my network. when i go to computer management, operating system deployment, boot images and then when i go to the x86 bot image and then go to distribution point and right click distribution points and add a new distribution point at the package status thingy it keeps hanging on "install retrying" it says this in the dstmgr.log:

Hi,

I have problem here. After the OSD deployment I can now find all my machines are now assigned to the Primary site as well as secondary site. There are two entries in the al systems collection, one has the primary site code where the client is approved and other is the secondary server which do not have approved client.

This creating issues when I am pushing applications by using AD security groups. 

Can anybody throw some light into this.

Thanks

Rakesh Sahoo

Hello all,

I have ran in to an issue I have not seen before.  While attempting to setup a new DP the config manager will not install.  I set the DP up under site systems and it is listed under site systems but when I go to the DP the smspkgc$ and smsig$ folders are not created.  Also, the configmgr doesn't show up under control panel and the CCM folder is not under syswow64.  Over the course of the last week I 3 times tried removing the DP from site systems, waiting 24 hours and then reinstalling it but I get the same result every time.  I have tried rebooting the SCCM server and the DP multiple times.  Here is another interesting thing.  I can copy packpages to the DP with the SCCM server just like I can any other DP bbut I can not push packages from the DP to the client.  We have 7 DP's total and the rest of them are working fine.

Any ideas?

Thanks!

Hello,

i have:

- SCOM 2007 R2 installed on W2k8 R2 64bits

- HP OVO interop installed  on W2k8 R2 64bits



At the end of installation, wizzard is able to communicate with my Interop connector, but certificate retrieval always in fault.



Ouput:

scicert.exe LMON1WSIS11V01 <local_admin> <pwd> "OpsMgr Connector for HP OpenView Operations"
Connecting to: https:local_admin@LMON1WSIS11V01:1270
ERROR: WSManLibException caught ==>
-- Error in method WSManSession::Execute --
<f:WSManFault xmlns:f="http:schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="1359" Machine="LMON1WSIS11V01"><f:Message><f:ProviderFault provider="WMI Provider" path="%systemroot%\system32\WsmWmiPl.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="1359" Machine="LMON1WSIS11V01.fr."><f:Message>HRESULT = 0x80041013</f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>
Error number: 0x8007054f



I try with this:

winrm enumerate http:schemas.microsoft.com/wbem/wsman/1/wsmanfault auth:basic -remote:https:lmon1wsis11v01:1270 -username:local_admin -password:pwd -skipcncheck -skipcacheck

result is KO

WSManFault
    Message = The WS-Management service cannot process the request. The resource URI (http:schemas.microsoft.com/wbem/wsman/1/wsmanfault) was not found in the WS-Management catalog. The catalog contains the metadata that describes resources, or logical endpoints.
Error number:  -2144108485 0x8033803B

winrm enumerate http:schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_Service auth:basic -remote:https:lmon1wsis11v01:1270 -username:local_admin -password:pwd -skipcncheck -skipcacheck

result is good and services are displayed

So i wonder what could be the root cause of my issue, because the schemas that Connector try to reach seem unavailable !!

I uninstall and reinstall both connectors several times, with domain administrator and local admin, same result.



In documenation it says that we should transfer certificate manually, but procedure still bases on remote query. I try following this thread:

http:blogs.technet.com/b/stefan_stranger/archive/2011/08/16/lessons-learned-the-opsmgr-2007-r2-universal-connector.aspx

i copy the Interop certificate on OPS Connector and run the command 

scxcertconfig.exe" -sign c:\LMON1WSIS11V01.cer c:\LMON1WSIS11V01_sign.cer

Output:

Signing failed: Can't decode from base64





Please any help will be appreciate

EDIT: url link are well formated, i remove the // to prevent microsoft check that not allows me to post any link...

 these days , our win-serv administrator approved a couple of updates for security needs ,so my sccm site server (which runs ConfigMgr2007 ,sql 2005 and server2003 64bit,we plan to update to ConfigMgr 2012 in the nearly future) installed updates and i restart to make updates work .

then comes a problem about SMS_MP_CONTROL_MANAGER. when i check sccm working status, i can not access to both  /sms_mp/.sms_aut?mplist and  /sms_mp/.sms_aut?mpcert. the page shows me 'services unavailable'

so i come to configmgr console to confirm the question,and i find message id 5480 in SMS_MP_CONTROL_MANAGER. it points out error result (error code 503 )and some possible reasons and leads me to kb838891(http://support.microsoft.com/kb/838891/en-us). when i use setup.exe /prereq to validate prerequisites of the site system(about mp,sql instance,sql spn properties),these's no any errors but some warnings....

then i find a similar post here:http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/720b59d6-55b9-4c27-b4c0-c0ae426ecfe2

John Marcum said If neither work figures out IIS problem.

And in later posts i find ' So for the other lost souls out there trying to find the answer to getting your MP working on a 64 bit server - check out the IIS settings - Application Pools - SMS Management Point Pool x64 - click on advanced settings - Enable 32-Bit Applications should be set to False. '

i can not check this setting in iis6....how can i validate it and set it to false if needed? i know it's really easy in server 2008 with iis7....

thx

Hello,

I have tried running the Client Push wizard for a single computer or a pilot collection of 8 computers, the result is always

the same - no SCCM client is installed on any computer.

The computers are running 32-bit Windows XP SP2.

The Windows firewall is disabled.

The client push installation account is setup and have domain admin and local admin privileges. Client Push automatic method

is not enabled.

The domain is AD WIndows 2000.

The SCCM server is running Windows 2003 R2 SP2 64bit Standard.

The AD schema has been extended.

MP, and SLP are installed and published. (MP is published in DNS as well.)

FSP is installed.

MP, SLP and FSP are running on the same server.

SQL 2005 server is running locally.

System management container is created and all rights and permissions delegated.

With the Push installation account I can access C$ share on the client computer from the SCCM server.

RPC, Remote registry, WMI services are running on the client machines.

All prerequisites are installed from the client folder on SCCM server- latest BITS 2.5, Windows installer 3.1 and MSXML6.

All computers are in the same IP subnet which is listed in the boundaries.

Yet, the client is not being installed.

No CCMSetup folder is created on the client machines in Windows\System32 folder, so it is really difficult to troubleshoot

what the is the issue. I do not see anything helpful in the ccm.log on the server.

I have tried running the CCMSetup.exe manually on one of the workstations and that was successful and reported back to the

SCCM server / console.

What else I should check / try? I really want to push agents via the wizard.

Thank you,

Peter

I'm using the script referenced in another discussion here.  I'm not sure why the client in not being installed, or the corrective action to take.

Pointers?

<![LOG[---------- Beginning Execution]LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Opened configuration file: ConfigMgrStartup.xml]LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Loading Options and Parameters from configuration file]LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Option loaded: SiteCode: 'Auto']LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Option loaded: CacheSize: '8120']LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Option loaded: AgentVersion: '4.00.6487.2000']LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Option loaded: MinimumInterval: '0']LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Option loaded: ClientLocation: '\\deployment\sms_fll\Client']LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Option loaded: MaxLogFile: '2048']LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Option loaded: ErrorLocation: '\\deployment\BadLogs']LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Verifying Last Run time from Registry: HKLM\Software\ConfigMgrStartup\Last Run]LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Last run time was 8/25/2011 4:04:09 PM]LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[Successfully Connected to WMI]LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[START: Service Check...]LOG]!><time="16:16:20.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *BITS...found (Stopped,Auto)...expected State of Running...started service...OK]LOG]!><time="16:16:36.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *winmgmt...found (Running,Auto)...OK]LOG]!><time="16:16:36.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *wuauserv...found (Stopped,Auto)...expected State of Running...started service...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *lanmanserver...found (Running,Auto)...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *RpcSs...found (Running,Auto)...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[START: Admin Share Check...]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *Admin$...found...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[START: Registry Check...]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *HKLM\SOFTWARE\Microsoft\Ole\EnableDCOM...found (Y)...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *HKLM\SOFTWARE\Microsoft\Ole\EnableRemoteConnect...not found...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="2" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *HKLM\SOFTWARE\Microsoft\Ole\LegacyAuthenticationLevel...not found...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="2" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *HKLM\SOFTWARE\Microsoft\Ole\LegacyImpersonationLevel...found (2)...OK]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[START: Checking Client Status...]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *Cannot connect to ConfigMgr WMI Namespace: -2147217394]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="2" thread="" file="ConfigMgrStartup.vbs">
<![LOG[START: Client Install...]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">
<![LOG[ *Initiating client install with command-line: \\deployment\sms_fll\Client\ccmsetup.exe SMSCACHESIZE=8120 SMSSITECODE=Auto]LOG]!><time="16:16:53.000+0" date="8-25-2011" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs">

My company is a child domain and we have our own SCCM 2007 system setup, one of the divisions of the parent domain also has SCCM 2007 setup.  One of their SCCM admins added the 192.168.0.0/16 subnet to their boundaries to try to get internet client management.  The parent AD's network staff have set all of 192.168.x.x to be routable.  This however has had an adverse affect on our clients that connect through VPN and first get a 192.168.x.x address from their home router in that software will never deploy to a computer at home, and if you go to Advanced under Configuration Manager Properties and do a discover their Site Code shows up instead of ours.  We have blocked their site server on our firewall and that works internally if someone is running a virtual machine that gets an address in that range.  Is there anything we can do to stop this from happening and causing issues with our deployment and management of the client computers?

We have moved to the 2008 R2 platform and are staying with SCCM 2007 R2 for now. 

There seems to be a problem with advertised packages not showing up for almost 24 hours on a client machine.  Previously on the 2003 R2 platform we didnt have the problem so Im concenred I may have missed something.  Ive screened the Client Location log and seen where the client is continously trying to get the assisgned site (which then gets and is assisnged to the proper site code).  However, it does this over and over.  In a 20 minute time period it has requested and was subsequently assigned 5 times.

Ive also reviewed the LocationServices log and it is attempting to retrieve the local MP from AD and states it has retrieved the correct MP and refreashes the MP with the correct site code. (It also refreashes the certificate keys as well)

The Schema has been extended, the management services container has the correct permissions, and the site can publish to AD (SLP and Wins have also been properly configured ... just in case)

We didnt have this proplem on the 2003 box but the 2008 R2 is proving to be difficult. 

One last log I did look at was the execmgr log and found nothing but red (see below)

All these logs are off of a new client install.  The server logs will be reviewed later tonight.

Thanks for any insight!

v/r

Hi, while proceeding to clean up the deletion of a child site in SCCM 2007 using "Preinst /Delsite xyz" command, I erroneously typed the wrong site code. This action resulted in a the wrong child site to be removed from the Admin console, although the SCCM files are OK on the site server.

Is there a way to recover the child site "xyz" in the database?

Thanks,

Silvio