i got this error

--> ERROR: Unable to access target machine for request: "2097154595", machine name: "L31",  access denied or invalid network path.SMS_CLIENT_CONFIG_MANAGER4/19/2013 9:51:26 PM9872 (0x2690)

Execute query exec [sp_CP_SetLastErrorCode] 2097154595, 53SMS_CLIENT_CONFIG_MANAGER4/19/2013 9:51:26 PM9872 (0x2690)

We run a monitoring tool on our servers and it shows that the SMS Agent service keeps stopping and starting... Is this normal?

Team,

I have deployed patches for last two months and extracted the enforcement report. As per the report, failed to update count is tolled to 30%. (1500+ machines)

Please help me how to handle this situation and increase the complaint level. SCCM Client failed to install some updates, I have a SCCM 2007. Please advice.

Regards, Dev

We are running in Mixed Mode and we do not have any certs on the workstations.   Yet when I look in our All Systems collection we have about 5% of our machines showing up as APPROVED=N/A or APPROVED=Not Approved.

Why and how do we make them all equal APPROVED?

---

mqh7

I am trying to test deployments against a virtual machine running on ESX 5.1. The system I have deployed is basically an XP VM, but I never let it fully boot. I do a network boot. This works and PXE starts and loads the x86 image. After that WinPE loads and indicates the configuration files are being loaded. After that, where I would normally expect a prompt for what image to install, I just get a grey screen with the system centre logo. After about a minute the machine reboots.

I have tried searching for this and most hits I get that describe this problem are not getting as far as the GUI loading. In addition, they mention log files that I can't find on this machine.

This is 2012SP1. I couldn't find a forum for 2012 and others seem to be posting 2012 questions here. So hopefully this is the right place.

I created a new advertisement for a package. I did the machine policy refresh for the particular collection. When I tried to open the SMS report it brings four options in it.

No status

Accepted

Accepted - No further status

Succeeded

I am able to get the reports of No status and Succeeded. But whenever I try to open the other two options it brings Page cannot be displayed. I dont know what it means.

Can anyone help me in this please.

 

Shall we able to Migrate an existing SCCM environment to New Domain?

Pls Help..

Hi,

windows 2008 R2 + SCCM 2007 SP2 +r3

We are trying to push sccm client. out of 1200 machines, 400 machines install the sccm client well and rest of the machines get error as below.  we have set the right permission on webdav.

DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Client OS Version is 5.1, Service Pack Version 3 ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Client OS is not a supported Windows Embedded Platform ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Waiting for existing instances of ccmsetup to exit. ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Deleted file C:\WINDOWS\system32\ccmsetup\ccmsetup.exe.download ccmsetup 5/3/2011 6:50:51 PM 3524 (0x0DC4)
All other instances of ccmsetup have completed. ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Successfully ran BITS check. ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Failed to receive WinHttp response. (Error at WinHttpReceiveResponse: 12152) ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
DownloadFileByWinHTTP encountered an unrecoverable error. ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
Sending Fallback Status Point message, STATEID='308'. ccmsetup 5/3/2011 6:50:51 PM 2660 (0x0A64)
receiving response with winhttp failed; 80072f78 FSPStateMessage 5/3/2011 6:50:51 PM 2660 (0x0A64)

[SC 2012 SP1 beta][OSD] not able to activate the "Apply" by using SetDirtyFlag or use "dirty" property

We face an issue when do the OSD OEM integration with SCCM 2012 SP1 beta. In task sequence editor, we add our customized step action control, and follow the step as MSDN indicated:http://msdn.microsoft.com/en-us/library/cc143499.aspx . We want to active the"apply" button in task sequence editor by using the API SetDirtyFlag(true) or Dirty = true when things changed in our action control. However, "apply" button is not enabled after call this method.

We use the same logic to perform this task, and no issues happened on SCCM 2007 R2 or SCCM2012. 



SCCM2012SP1beta has this kind of issue, but SCCM2007R2/2012 don't.

Env: windows2008r2 + SCCM2012SP1 beta
Steps to Reproduce:  (steps could be found on MSDN http://msdn.microsoft.com/en-us/library/cc143499.aspx )
1. find the required dll under C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin on SCCM2012SP beta server, and reference these assemblies in my own project
---assemblies list----
 AdminUI.Common.dll
 AdminUI.DialogFoundation.dll
 AdminUI.OsdCommon.dll
 AdminUI.TaskSequenceEditor.dll
 AdminUI.WqlQueryEngine.dll
 Microsoft.ConfigurationManagement.ApplicationManagement.dll
 Microsoft.ConfigurationManagement.ApplicationManagement.Extender.dll
 Microsoft.ConfigurationManagement.DialogFramework.dll
 Microsoft.ConfigurationManagement.exe
 Microsoft.ConfigurationManagement.exe.config
 Microsoft.ConfigurationManagement.ManagementProvider.dll
------------------------

2. add event handler to my customized action control, e.g. for a text field, add an event handler once content changed. In the handler, set dirty flag by 
leverage the API "Microsoft.ConfigurationManagement.AdminConsole.SmsPageControl.SetDirtyFlag(bool" to active the "apply" button as we always do. Since this method is deprecated in SP1 dll, we also try set "Dirty" property to "true" as indicated. However, neither of them succeed to enable the "apply" button

---code---
SetDirtyFlag(true);
//Dirty = true;
3. however the "apply" button doesn't active at all. if we click "ok" button, the changes doesn't save either.

the user will not be able to save the any changes in my customized action control. It will be very annoying. So it is a must fix defect.

Sometimes my company has the need to remove computers from the domain. The reason is that the computer either will not have internet easily accessible or the computer will not be connected to any sort of network.

We want to automate the procedure remove a computer from domain and then register the mak key. The question is what is the best way of doing it? I've been thinking that a task sequence can get the job done. However, I'm a bit unsure how such a task sequence should be built.

My current Task sequence looks currently like this:

Join WorkGroup

Restart Computer

Apply Windows Settings - where I add the MAK key as well as enable the local administrator

Apply MAK key for Windows 7 - runs the command "cscript.exe c:\windows\system32\slmgr.vbs /ato" to enable the MAK key.

The question is wheter I'm on the right path or if I should do it differently.

Hi

Is it possible to transfer sccm software metering data from one sccm site to another. We are building new SCCM 2007 and customer wants to keep old software metering data for reporting purposes. Clients will remain we change site usin GPO.

Is it possible to import that data?

br Veikka

Im trying to install a Secondary site for our SCCM 2012 with Sp1 separated over Wireless in another Site but it ends up with the following error after the Pre-requisites Checks are passed and the entry to registry fails with following error

 ERROR: Failed to update prerequisite results into the registry; error = 1.

Any help will any highly appreciated from the Professionals in this field

I have included the Configmgrprereq.log as below

<05-15-2013 16:59:05> ******* Start Prerequisite checking. *******
<05-15-2013 16:59:05> ********************************************
<05-15-2013 16:59:05> Commandline :
"E:\Microsoft Configuration Manager\bin\x64\smsexec.exe"
<05-15-2013 16:59:05> Check Type: Secondary site 
 Site Server: SEJED-SCCM01.nmc.com,
 SQL Server: SEJED-SCCM01.nmc.com,
 SQL Named Instance: ,
 Install Folder: C:\Program Files\Microsoft Configuration Manager\,
 Setup Source Folder: \\192.168.100.88\sccmEP2012Setup
<05-15-2013 16:59:05> INFO: Executing prerequisite functions...
<05-15-2013 16:59:05> ===== INFO: Prerequisite Type & Server: SITE_SEC:SEJED-SCCM01.nmc.com =====
<05-15-2013 16:59:05> <<<RuleCategory: Access Permissions>>>
<05-15-2013 16:59:05> <<<CategoryDesc: Checking access permissions...>>>
<05-15-2013 16:59:05> INFO: CheckLocalSys is Admin of <SEJED-SCCM01.nmc.com>.
<05-15-2013 16:59:13> SEJED-SCCM01.nmc.com;    Site server computer account administrative rights;    Error;    Configuration Manager Setup requires that the site server computer has administrative rights on the SQL Server and management point computers.
<05-15-2013 16:59:13> <<<RuleCategory: System Requirements>>>
<05-15-2013 16:59:13> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<05-15-2013 16:59:13> INFO: Check Lanman service: <SEJED-SCCM01.nmc.com>.
<05-15-2013 16:59:14> ERROR: Failed to connect to WMI namespace on SEJED-SCCM01.nmc.com
<05-15-2013 16:59:16> ERROR: Failed to call GetResultByRunningService
<05-15-2013 16:59:16> SEJED-SCCM01.nmc.com;    Check Server Service is running;    Error;    Setup is unable to verify that the Server Service is started.
<05-15-2013 16:59:16> INFO: OS version:0, ServicePack:0.
<05-15-2013 16:59:16> SEJED-SCCM01.nmc.com;    Unsupported site server operating system version for Setup;    Error;    Configuration Manager site systems can only be installed on systems running Windows Server 2008 SP2 or later.
<05-15-2013 16:59:16> INFO: Failed to get Active Directory membership information for computer SEJED-SCCM01.nmc.com with 0.
<05-15-2013 16:59:16> SEJED-SCCM01.nmc.com;    Domain membership;    Error;    Configuration Manager site server components must be installed on computers that are members of a Windows domain.
<05-15-2013 16:59:16> ERROR: Failed to check Free space on target dir \\SEJED-SCCM01.nmc.com\C$\.
<05-15-2013 16:59:16> SEJED-SCCM01.nmc.com;    Free disk space on site server;    Error;    The site server computer must have at least 5GB of free disk space to install the site server. If the SMS Provider site system role will be installed on the same computer, you must have an additional 1GB of free disk space.
<05-15-2013 16:59:17> SEJED-SCCM01.nmc.com;    Pending system restart;    Passed
<05-15-2013 16:59:17> INFO: The server SEJED-SCCM01.nmc.com is not read-only domain controller.
<05-15-2013 16:59:17> SEJED-SCCM01.nmc.com;    Read-Only Domain Controller;    Passed
<05-15-2013 16:59:18> INFO: Check FQDN Length for site server: <SEJED-SCCM01.nmc.com>.
<05-15-2013 16:59:19> SEJED-SCCM01.nmc.com;    Site Server FQDN Length;    Passed
<05-15-2013 16:59:19> <<<RuleCategory: Dependent Components>>>
<05-15-2013 16:59:19> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<05-15-2013 16:59:19> SEJED-SCCM01.nmc.com;    Microsoft XML Core Services 6.0 (MSXML60);    Warning;    MSXML 6.0 or later libraries are required for Configuration Manager console and Configuration Manager site server installations. MSXML 6.0 is available for download at http://go.microsoft.com/fwlink/?LinkId=215744
<05-15-2013 16:59:19> SEJED-SCCM01.nmc.com;    Microsoft Remote Differential Compression (RDC) library registered;    Error;    Microsoft Remote Differential Compression (RDC) library must be registered for Configuration Manager site server installation. Details at http://technet.microsoft.com/library/cc431377.aspx#RDC_for_Site_Servers.
<05-15-2013 16:59:19> INFO: Checking Windows Installer version on SEJED-SCCM01.nmc.com.
<05-15-2013 16:59:20> INFO: Path of Windows Installer is <\\SEJED-SCCM01.nmc.com\C$\Windows\System32\msi.dll>.
<05-15-2013 16:59:20> ERROR: Failed to determine Windows Installer version from path:<\\SEJED-SCCM01.nmc.com\C$\Windows\System32\msi.dll> .
<05-15-2013 16:59:20> SEJED-SCCM01.nmc.com;    Microsoft Windows Installer;    Error;    Setup failed to verify the Windows Installer version, or the installed version of Windows Installer does not meet the minimum requirement.  Configuration Manager requires at least Windows Installer version 4.5.
<05-15-2013 16:59:21> INFO: Start Checking InstallSQLExpress on site server: SEJED-SCCM01.nmc.com, SQL Server instance CONFIGMGRSEC
<05-15-2013 16:59:21> INFO: SQL Server Express installation was not selected.
<05-15-2013 16:59:21> SEJED-SCCM01.nmc.com;    SQL Server Express on Secondary Site;    Passed
<05-15-2013 16:59:21> ERROR: Failed to connect to registry of SEJED-SCCM01.nmc.com
<05-15-2013 16:59:21> SEJED-SCCM01.nmc.com;    Existing Configuration Manager server components on site server;    Error;    A site server or site system role is already installed on the computer selected for site server installation. Remove the site or site system role from the computer, or select another computer for site server installation.
<05-15-2013 16:59:21> SEJED-SCCM01.nmc.com;    Firewall exception for SQL Server (stand-alone primary site);    Passed
<05-15-2013 16:59:21> INFO: SQL Server computer <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:21> INFO: SQL Server named instance <>
<05-15-2013 16:59:21> SEJED-SCCM01.nmc.com;    SQL Server service running account;    Error;    The logon account for the SQL Server service cannot be a local user account, NT SERVICE\<sql service name> or LOCAL SERVICE.  You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.
<05-15-2013 16:59:21> INFO: SQL Server computer <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:21> INFO: SQL Server named instance <>
<05-15-2013 16:59:21> INFO: Cannot connect to registry key.
<05-15-2013 16:59:21> SEJED-SCCM01.nmc.com;    Dedicated SQL Server instance;    Passed
<05-15-2013 16:59:21> INFO: CheckSQLCollationSecondary
<05-15-2013 16:59:22> INFO: Collation on <prjed-sccm01.nmc.com> <SQL_Latin1_General_CP1_CI_AS>
<05-15-2013 16:59:25> ERROR: failed to get collation from secondary site
<05-15-2013 16:59:25> SEJED-SCCM01.nmc.com;    Parent/child database collation;    Error;    The collation of the site database does not match the collation of the parent site's database.  All sites in a hierarchy must use the same database collation.
<05-15-2013 16:59:25> INFO: Checking .NET framework versions 3.5...
<05-15-2013 16:59:26> ERROR: Cannot connect to key SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5 on SEJED-SCCM01.nmc.com
<05-15-2013 16:59:26> INFO: .NET is not installed.
<05-15-2013 16:59:26> SEJED-SCCM01.nmc.com;    Minimum .NET Framework version for Configuration Manager site server;    Error;    The Microsoft .NET Framework 3.5 is required for Configuration Manager site server installation. For Windows Server 2008, you can download the Microsoft .NET Framework 3.5 from http://go.microsoft.com/fwlink/?LinkId=185604.  For Windows Server 2008 R2, you can enable the Microsoft .NET Framework 3.5 as a feature within Server Manager.
<05-15-2013 16:59:26> INFO: CheckInstallSourceVersion <\\192.168.100.88\sccmEP2012Setup>
<05-15-2013 16:59:26> SEJED-SCCM01.nmc.com;    Setup Source Version;    Passed
<05-15-2013 16:59:26> INFO:CheckInstallSourcePath <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:27> ERROR: Failed to call GetResultByRunningService
<05-15-2013 16:59:27> SEJED-SCCM01.nmc.com;    Setup Source Folder;    Error;    The computer account for the secondary site must have Read NTFS and share permissions to the Setup source folder and share. We recommend that you do not use administrative shares (for example, C$ and D$) because they require the secondary site computer account to be an administrator on the remote computer.
<05-15-2013 16:59:27> INFO: Enter CheckSecSiteSqlOnSameMachine.
<05-15-2013 16:59:27> INFO: Target secondary site Machine <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:27> INFO: SQL Server computer <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:28> SEJED-SCCM01.nmc.com;    SQL Server on the Secondary Site Computer;    Passed
<05-15-2013 16:59:28> INFO:CheckSupportedFQDNFormat <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:28> ERROR: Failed to extract NetBIOS name from <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:28> SEJED-SCCM01.nmc.com;    Primary FQDN;    Error;    Configuration Manager only supports the use of primary FQDN’s, where the DNS hostname (first label in the FQDN) matches the NetBIOS hostname of the computer.  The FQDN provided for this site system does not meet this requirement and cannot be used.  Correct the FQDN and try again.
<05-15-2013 16:59:28> INFO:CheckMachineAccountHasADAccess <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:29> ERROR: Failed to call GetResultByRunningService
<05-15-2013 16:59:29> SEJED-SCCM01.nmc.com;    Verify site server permissions to publish to Active Directory.;    Warning;    The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure required permissions, see http://go.microsoft.com/fwlink/p/?LinkId=233190.
<05-15-2013 16:59:30> INFO:CheckRemoteWMIConnection <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:38> SEJED-SCCM01.nmc.com;    Remote Connection to WMI on Secondary Site;    Warning;    Setup is unable to establish a remote connection to WMI on the secondary site. Typical causes can include network connectivity blocked by firewalls that are located on or between the computers, name resolution failures including some disjoint namespace configurations, or the configuration of WMI and access permissions on the remote computer. For information about WMI Troubleshooting, see http://go.microsoft.com/fwlink/?LinkId=254873. 
<05-15-2013 16:59:38> INFO: Check required collation of Sql Server.
<05-15-2013 16:59:38> INFO: LangID <409>
<05-15-2013 16:59:38> INFO: NOT primary site or CAS install, skipping check for reqired collation of SQL Server.
<05-15-2013 16:59:38> SEJED-SCCM01.nmc.com;    Required SQL Server Collation;    Passed
<05-15-2013 16:59:38> ===== INFO: Prerequisite Type & Server: SQL:SEJED-SCCM01.nmc.com =====
<05-15-2013 16:59:38> <<<RuleCategory: Access Permissions>>>
<05-15-2013 16:59:38> <<<CategoryDesc: Checking access permissions...>>>
<05-15-2013 16:59:38> INFO:RemoteCheckAdminOnSQL <SEJED-SCCM01.nmc.com>, SQL Server <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:40> ERROR: Failed to call GetResultByRunningService
<05-15-2013 16:59:40> SEJED-SCCM01.nmc.com;    SQL Server sysadmin rights;    Error;    Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.
<05-15-2013 16:59:41> ===== INFO: Prerequisite Type & Server: MP:SEJED-SCCM01.nmc.com =====
<05-15-2013 16:59:41> <<<RuleCategory: Access Permissions>>>
<05-15-2013 16:59:41> <<<CategoryDesc: Checking access permissions...>>>
<05-15-2013 16:59:41> SEJED-SCCM01.nmc.com;    Administrative share (Site system);    Passed
<05-15-2013 16:59:41> INFO:CheckSiteSystemtoSQLConnectivity <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:42> INFO: Installing secondary site, skipping SQL Server connectivity check.
<05-15-2013 16:59:42> SEJED-SCCM01.nmc.com;    Site System to SQL Server Communication;    Passed
<05-15-2013 16:59:42> <<<RuleCategory: System Requirements>>>
<05-15-2013 16:59:42> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<05-15-2013 16:59:42> INFO: The rule 'Check Server Service is running' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:42> INFO: OS version:0, ServicePack:0.
<05-15-2013 16:59:42> SEJED-SCCM01.nmc.com;    Unsupported management point operating system version for Setup;    Warning;    Configuration Manager site systems can only be installed on systems running Windows Server 2008 SP2 or later.
<05-15-2013 16:59:42> INFO: The rule 'Domain membership' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:42> WARN: Failed to check Windows Failover Cluster on SEJED-SCCM01.nmc.com, hr == 80070005.
<05-15-2013 16:59:42> SEJED-SCCM01.nmc.com;    Windows Failover Cluster;    Passed
<05-15-2013 16:59:42> INFO: The rule 'Pending system restart' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:42> <<<RuleCategory: Dependent Components>>>
<05-15-2013 16:59:42> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<05-15-2013 16:59:42> INFO: The rule 'Microsoft XML Core Services 6.0 (MSXML60)' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:42> SEJED-SCCM01.nmc.com;    IIS service running;    Warning;    Internet Information Services (IIS) is required for some site system roles. You have selected to install a site system role that requires IIS. Install IIS on the site system to continue setup.
<05-15-2013 16:59:44> ERROR: Failed to get WEBSVCEXT from Remote Service on SEJED-SCCM01.nmc.com.
<05-15-2013 16:59:44> INFO: Failed to get IIS BITS Server Extensions state on SEJED-SCCM01.nmc.com.
<05-15-2013 16:59:44> SEJED-SCCM01.nmc.com;    BITS installed;    Warning;    Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS is not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings.
<05-15-2013 16:59:45> ERROR: Failed to get WEBSVCEXT from Remote Service on SEJED-SCCM01.nmc.com.
<05-15-2013 16:59:45> INFO: Failed to get IIS BITS Server Extensions state on SEJED-SCCM01.nmc.com.
<05-15-2013 16:59:45> SEJED-SCCM01.nmc.com;    BITS enabled;    Warning;    Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS is not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings.
<05-15-2013 16:59:45> SEJED-SCCM01.nmc.com;    IIS HTTPS Configuration for management point;    Passed
<05-15-2013 16:59:45> INFO: Stand-alone primary site or secondary site. Skip checking firewall settings for SQL Server
<05-15-2013 16:59:45> SEJED-SCCM01.nmc.com;    Firewall exception for SQL Server for management point;    Passed
<05-15-2013 16:59:46> SEJED-SCCM01.nmc.com;    Administrative rights on management point;    Passed
<05-15-2013 16:59:46> INFO:CheckV4ClientNotInstalled <SEJED-SCCM01.nmc.com>
<05-15-2013 16:59:47> ERROR: Failed to call GetResultByRunningService
<05-15-2013 16:59:47> SEJED-SCCM01.nmc.com;    Client Version on Management Point Computer;    Warning;    You cannot install the management point on a computer with an earlier version of the Configuration Manager client installed. Upgrade the client to the current version, remove the client, or select a different computer for the management point installation, and then try again.
<05-15-2013 16:59:50> ===== INFO: Prerequisite Type & Server: DP:SEJED-SCCM01.nmc.com =====
<05-15-2013 16:59:51> <<<RuleCategory: Access Permissions>>>
<05-15-2013 16:59:51> <<<CategoryDesc: Checking access permissions...>>>
<05-15-2013 16:59:51> <<<RuleCategory: System Requirements>>>
<05-15-2013 16:59:51> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<05-15-2013 16:59:51> SEJED-SCCM01.nmc.com;    Unsupported distribution point operating system version for Setup;    Warning;    Configuration Manager distribution point can only be installed on systems running Windows Server 2003 or later.
<05-15-2013 16:59:51> INFO: The rule 'Domain membership' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:51> INFO: The rule 'Windows Failover Cluster' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:51> INFO: The rule 'Pending system restart' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:51> <<<RuleCategory: Dependent Components>>>
<05-15-2013 16:59:51> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<05-15-2013 16:59:51> SEJED-SCCM01.nmc.com;    Microsoft XML Core Services 6.0 (MSXML60) for distribution point;    Warning;    MSXML 6.0 or later libraries are required for Configuration Manager console and Configuration Manager site server installations. MSXML 6.0 is available for download at http://go.microsoft.com/fwlink/?LinkId=215744
<05-15-2013 16:59:51> INFO: The rule 'IIS service running' has been run on server 'SEJED-SCCM01.nmc.com', skipped.
<05-15-2013 16:59:51> SEJED-SCCM01.nmc.com;    IIS HTTPS Configuration for distribution point;    Passed
<05-15-2013 16:59:51> SEJED-SCCM01.nmc.com;    Administrative rights on distribution point;    Passed
<05-15-2013 16:59:51> ***************************************************
<05-15-2013 16:59:52> ******* Prerequisite checking is completed. *******
<05-15-2013 16:59:52> ***************************************************
<05-15-2013 16:59:52> INFO: Updating Prerequisite checking result into the registry
<05-15-2013 16:59:52> INFO: Connecting to SEJED-SCCM01.nmc.com registry
<05-15-2013 16:59:52> INFO: Setting registry values
<05-15-2013 16:59:52> ERROR: Failed to update prerequisite results into the registry; error = 1.

---

FBM

Hi-

Our server is SCCM SP2. Client is Windows 7Pro.

Client push is on and working just fine.

I am writing a batch file to call the ccmsetup.exe from the netlogon share. This worked the first time. Then after uninstalling the client and trying a resinstall I get the error below. This same error happens even though I reimaged the machine. Client push works fine. Manual I get the embedded error message which the OS is not embedded. Why would CM work the first time then and subsequent install attempts detect the OS as embeded thus unsupported? I left the server name but took out the domain name in this log file so I could post it: 


<![LOG[Detected 56942 MB free disk space on system drive.]LOG]!><time="10:55:42.720+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:463">
<![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="10:55:42.720+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:509">
<![LOG[Client OS Version is 6.1, Service Pack Version 0]LOG]!><time="10:55:42.720+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:533">
<![LOG[Client OS is not a supported Windows Embedded Platform]LOG]!><time="10:55:42.720+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:535">
<![LOG[Successfully ran BITS check.]LOG]!><time="10:55:42.813+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:7105">
<![LOG[IsFileMicrosoftTrusted Verified file 'C:\Windows\system32\ccmsetup\ccmsetup.cab' is MS signed.]LOG]!><time="10:55:43.219+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:1207">
<![LOG[Successfully extracted manifest file C:\Windows\system32\ccmsetup\ccmsetup.xml from file C:\Windows\system32\ccmsetup\ccmsetup.cab.]LOG]!><time="10:55:43.219+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:7233">
<![LOG[Loading manifest file: C:\Windows\system32\ccmsetup\ccmsetup.xml]LOG]!><time="10:55:43.219+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="manifest.cpp:93">
<![LOG[Successfully loaded ccmsetup manifest file.]LOG]!><time="10:55:43.219+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="manifest.cpp:105">
<![LOG[Couldn't get directory list for directory 'http://S00SCCM01/CCM_Client/ClientPatch'.  This directory may not exist.]LOG]!><time="10:55:43.234+240" date="03-14-2011" component="ccmsetup" context="" type="0" thread="2716" file="ccmsetup.cpp:6215">
<![LOG[Adding file 'http://S00SCCM01:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\Windows\system32\ccmsetup\client.msi'.]LOG]!><time="10:55:43.359+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:6613">
<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='309' will not be sent.]LOG]!><time="10:55:43.359+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:9330">
<![LOG[Deleted file C:\Windows\system32\ccmsetup\ccmsetup.cab]LOG]!><time="10:55:43.437+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:9069">
<![LOG[Deleted file C:\Windows\system32\ccmsetup\ccmsetup.xml]LOG]!><time="10:55:43.437+240" date="03-14-2011" component="ccmsetup" context="" type="1" thread="2716" file="ccmsetup.cpp:9069">

 

 I have a question from client security manager -what is the impact if we remove theSoftware\Microsoft\SMS from the following security policy setting: Location:Computer Configuration / Windows Settings / Security

The following registry paths have been configured to be accessible remotely:

For a 32-bit operating system: HKEY_LOCAL_MACHINE\Software\Microsoft\SMS

For a 64-bit operating system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS

Allowing remote access to registry paths, over and above those configured by default, may create additional areas of exposure allowing a remote authenticated attacker to access information that would not normally be available.

Any registry path that is found to not require remote access for the normal operation of the systems should be removed. This can be accomplished by removing the appropriate entry from the following security policy setting: Location:Computer Configuration / Windows Settings / Security

Settings / Local Policies / Security Options : Network access: Remotely accessible registry paths and sub-paths

---

Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

Hi,

I am migrating a management point from one server to another
for a particular SCCM 2007 site.

I wanted to know during the migration is there any reason
during that migration I can't have a management point on
both servers at the same time?

I then plan on removing the role from one of them and I assume
then the clients will look to the other one as the default
management point?

Will this approach pose any issues?

Thanks,

Ward

Hi there,

after integrating ACT Connector 5.5 in ConfigMgr and deploying a data collector package i'd like to use the included reports.
when selecting a report like 'Application Compatibility Toolkit application status for a specific collection' i get an error

'The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "ACT-DB" under the current security context.'

ACT-DB surely is the DB created for Application Compatibility Toolkit.

i even receive the error when NT AUTHORITY\SYSTEM has the db_owner role.

When running 'Availability of device drivers required in the driver catalog for a specific collection' i get the error

'Cannot insert the value NULL into column 'HardwareIDs', table 'tempdb.dbo.#DeviceDrivers.....'

i used the ActConfig.vbs to workaround the error in the act connector when setting up the database.

does anyone have a hint?

thanks in advane

is it possible we can install two different sccm servers one for workstations and other one to manage servers is it possible?

This is my first time setting up a secondary site (sccm 2007 r2) and I'd like to know if there is a good way to test that it is working properly. I have to setup some secondary sites with some fairly slow links and I want to make sure it's not pulling data from our main central site. I have setup a secondary site with an AD site boundary. I have tested by deploying a package to a distribution point setup at the secondary site. The package successfully deployed, but I'd like to reassure myself that it is working the way it should be.

Thanks in advance.

Mike

Quick simple question that I can't seem to find the answer too!

Which account does SCCM 2007 use when running an AD System Discovery?

I want to deny access on certain AD OUs, so that these systems are not discovered and added to SCCM. I'd rather do it this way than including all the other OUs in the System Discovery properties.

Hi,

SCCM 2007 R3 on Win2008 R2 Std

I have a problem with SCCM Client, installation completes and i can see the Configuration Manager (32Bit) icon in the Control Panel but when i am trying to advertise packages it doesn't work  then i found that under Configuration Manager (32Bit) - Action - it shows only two items as in the screen below.

i checked the ccmsetup log file and found this warning message.

There is a similar case on this forum but its not exactly the same in my situation.

http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/3ee35189-ed41-4c69-a12d-74f70c7e36e1

and i followed these to fix this but still the same.

http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/dd605cc7-0510-4cae-83e5-cd3bd7b138c0/

 on this one it suggest manually uninstalling Microsoft WIMGAPI? but i am not sure how.

http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/2d56caeb-d439-415a-a499-e6566bae4215

1 - I tried Installing through GPO, manual and all other options Client 

2 - Restarting machine

3 - and i also used "SCCM Client Center (SMSCliCtr)" product to test the client machine from SCCM server everything seems to be fine.

I have seen this specifically happening with Win7 Enterprise OS now two cases so far.

Please suggest.

Regards,

Maqsood

---

Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified