Quantcast
Channel: Configuration Manager 2007 Setup/Deployment forum
Viewing all 443 articles
Browse latest View live

cannot installed client on computers

$
0
0

 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)


System Center 2012 Installation steps

$
0
0

Hi,

Can anyone please advise me with System Center 2012 Installation steps ?

Thank you

How to deploy KB923845 - Background Intelligent Transfer Service (BITS) 2.5 to clients?

$
0
0

Dears,

Hi

We want to deploy KB923845 - Background Intelligent Transfer Service (BITS) 2.5 to clients because SCCM installation on XP SP2 X64 fails and needs this update.

It seems that this update is not in WSUS so we can approve it for install to clients.

If it is available in WSUS please let me know which products and Classsifications should be marked,

If we cannot apprve in WSUS kindly advise a way.

SCCM 2007 SQL Database Move - Considerations for FEP 2010, WSUS and Reporting Services

$
0
0

We need to move our SCCM database to a new production SQL environment.

I have to hand a couple of articles (MS and Technet Blog) which explain the process for moving the SCCM database. However we also utilise FEP 2010, WSUS and Reporting Services. Are there any articles which explain any actions we need to take in respect of moving these databases?

Also, we're moving from a default instance to a named instance, any caveats other than officially only port 1433 is supported? Would a dynamic port work and would this be a recommended solution?

Many thanks

Stop SCCM Client Install

$
0
0

 

Hi,

 

I would like to exclude a bunch of computers from SCCM install. I plan to automate SCCM install and have 300-400 exceptions that should not obtain the client.

 

Any registry setting that I can play around with?

 

Thanks

Sandy

Slipstream CM07 SP2 R3

$
0
0

We currently have a CM07 SP1 slipstreamed and then we install all additional updates, hotfixes, and feature packs to get to CM07 SP2 R3 version. Any idea if and how i can create a slipstream for CM07 SP2 R3 directly?



SCCM Client - Missing configuration

$
0
0

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

Site Code Discovery Problem

$
0
0

 

Dear Friends;

I know that there are a lot of posts talking about the same issue, but I read all of them and many other searching results and tried all the solutions you provided with no luck. I got stuck in this issue since days and I am really very disappointed for not solving it till now.

Symptoms:

1-      SCCM 2007 client installed successfully in all clients machines.

2-      Site Code is not recognized in all clients machines

3-      you get the following error message when using discover button: "Automatic Site Code Discovery Was Unsuccessful"

4-      Components appear as installed but not enabled

5-      Under Actions, Just 2 actions appear.

6-      On SCCM sever all clients have Client=NO status

Cause:

Clients can’t get site code and by checking ClientLocation.log in all machines you will find that it just always try to get the assigned site and auto discover the site with no results.

Solutions and Configurations I tried:

1-      I've  already extended the  Schema and it was extended successfully

2-      I’ve created the System Management container in AD and updated the rights for the System container, the System Management container and all child objects ( MP, SLP, Site)

3-      SCCM is publishing properly to AD

4-      I’ve also add a SLP role to the same server and configure it well

5-      SCCM is also configured to publish to DNS ( although it is not needed)

6-      I tried many admin users for client push installation and all installed the client successfully with the same symptoms

7-      I don’t have any remarkable errors or warnings in the site status

8-      Boundaries are configured well: my customer has just one site and one domain and the boundary is the AD site.

9-      Manual installation of the client also does not solve the problem

10-   SMSSITECODE=ABC is configured in Client Push Installation Settings

11-   Windows firewall is turned off in all machines

12-   All clients run forefront antivirus

 

 

IMOPRTANT NOTE:

SMS 2003 was installed before on a Domain Controller and we uninstalled SMS 2003 properly and then installed SCCM 2007 SP1 on a new server. I feel that the problem is related to schema or AD, but how to confirm that? The schema was extended successfully, SCCM is publishing to AD, and all clients can contact the domain controllers.

 

I will really appreciate your help.

 

Thank you;

Alomari


Status Message Error 4964

$
0
0

Hello, 

I recently moved my SCCM Central Site from mixed mode to native mode. It's the only site in my site system. I went to check the status messages to see if the migration to native mode was succesful and I noticed that I keep getting the following to errors:

1. SMS_MP_COMPONENT_MANAGER error 4964 

2. SMS_MP_COMPONENT_MANAGER error 1020

Error 4964 says that Component manager failed to install this component because SSL is not configured properly on IIS. What are the configurations needed for SSL?

 

SCCM 2007 database move

$
0
0

Hi,

I successfully moved my DB to a clustered virtual MS SQL Server and followed all the steps from Microsoft.

But under Site Settings > Site Systems I don't see the clustered virtual MS SQL Servers listed, the old DB server no logner has the databse role which is expected.

So wondering why I don't see see the SQL cluster nodes displayed here? Anybody seen this before?

What actually happens when you initiate a client push installation? Can you trigger it via command line?

$
0
0

I'm building a custom application to audit different things about our network's computers so that it is all automated. One thing it is going to check is the "health" of the SCCM client based on it's last policy request date, hardware inventory, and heartbeat ddr. Usually I've found the only way to truly fix all of the problems is a complete uninstall of the client, remove the wmi namespace for ccm, and then launch a re-install. The first two actions I can automate just fine, but it's the last that is the problem. From some research (this helped http://myitforum.com/cs2/blogs/dhite/archive/2008/05/11/inside-the-configmgr-2007-mobileclient-tcf-file.aspx) and watching installs happen, I assume the following:

The site server uses the client install account to copy the ccmsetup.exe and mobileclient.tcf files to the client. The client then uses the mobileclient.tcf file to determine all of its installation properties and find the rest of the files to download from the MP. A few questions, if there are multiple management points, how does it determine which MP to use? Also, the article states that this only happens in mixed mode, what happens in native mode?

I also read this article: http://support.microsoft.com/kb/925282?wa=wsignin1.0, is it more accurate? A few questions on that article if it is,

1. During the pre-installation phase, SMS discovers the client computer and then generates a client configuration request (CCR) file. The CCR file contains the client computer name and additional information. - Where are the CCRs located on the site server before being moved to sms\inboxes\ccrretry.box?

Why are the following two steps conducted?

  • The SMS Client Configuration Manager connects to the ADMIN$ share on the client. This is based on the information in the CCR file.
  • The Client Configuration Manager connects to the client registry and gathers information about the client. This process is displayed as a log entry in the Ccm.log as connecting to IPC$.

Also the article states: Ccmsetup.exe downloads the client.msi file from the SMSClient\i386 shared folder on the SMS management point or from the Client\i386 folder in the SMS_<var>sitecode</var> shared folder on the SMS site server. This is in slight conflict with the other article (obviously I trust the microsoft article, but again, how does the client setup decide which server to use to download the additional files?)

I'd ideally like to either be able to initiate a client push install via command line (or if there's an API to do this, what is it?) or recreate the process through the custom application.

SCCM 2007 - Database move to a clustered virtual MS SQL Server

$
0
0

Hi,

I successfully moved my DB to a clustered virtual MS SQL Server and followed all the steps from Microsoft.

When I right click on my site and select properties uner Site Database > Site Management, I can see my SQL server is pointing to the new location and SCCM is functioning ok.

Also under System Status > Site Status > my site > Site System Status I can see the new location listed for the SQL Server.

But under Site Settings > Site Systems I don't see the clustered virtual MS SQL Servers listed, the old DB server no logner has the databse role which is expected.

So wondering why I don't see see the SQL cluster nodes displayed here? Anybody seen this before?

sccm update collection membership not updating

$
0
0
I have created a collection to deploy and test software with three desktops but they are not appearing when added, the hour glass stays on for ever and does not seem to populate.  Any suggestions of where one should be looking?

Help with recreating Secondry Site Server

$
0
0

I have just had to recreate my secondry site server as the drive died. I deleted the site from SCCM then installed windows 2008 and followed these steps.

I then reset up the site in SCCM and it looks like it started to copy files as I can see the D:\SCCM and this has all the program files and can also see it in program and features. And in the root of D:\ I can see it created a folder SMSPKGSIG but then it has not done anything for more then 48hours.

I have looked at the site status logs but there is nothing there that looks like an error.

Can anyone help me please?

SCCM 2007sp2 COLLECTION MEMBERSHIP IS NOT UPDATING

$
0
0

I have installed SCCM 2007sp2 in VMWare Workstation 8.0 with 2 Win2003 servers-one AD,another SCCM server. & 2 XP desktops. Collection is showing,but its membership is not updating-Trying for last 3 hours.

Please help. 

Suddhasattwa/suddhaman@gmail.com


How to ensure cache folder is created on fixed drive when using SMSCACHEFLAGS=MAXDRIVE ccmsetup.exe command line

$
0
0

Is there a way to ensure the SCCM client SMSCACHEDIR gets located on a local drive (as opposed to a temporary USB drive) when using the command line parameter SMSCACHEFLAGS=MAXDRIVE?

Our bog standard PCs have two logical partitions but with the advent of SSDs in tablets only 1 logical partition is created.

In SCCM the SMSCACHEDIR is located on the D: drive and the automated client push is configured as such; however this won't work for single partition machines - so we need to change the parameters in the client push settings but want to avoid accidently creating the the SMSCACHEDIR on an external USB drive the user maybe using when the SCCM client gets pushed.

Any pointers will be gratefully received.

Cheers

Simon

SCCM 2007 - Software Updates

$
0
0

Hi,

I recently moved my database from the local server to a cluster and today when I go to software updates select the current month i.e. May 2013 and update classification: Security Updates and click Go it comes back say "0 Software Updates found".

My configmgr software update point is on a seperate server.

What is the issue here?

ERROR: Failed to update prerequisite results into the registry; error = 1 for sccm 2012 secondary site installation

$
0
0

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

ERROR: Failed to update prerequisite results into the registry; error = 1 for sccm 2012 secondary site

$
0
0

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

Amending the scope of an SCCM site

$
0
0

Hi I have an issue whereby I need to remove two subnets from the scope of the SCCM site which is defined.

The way we have determined is best to proceed is to delete and recreate the site minus the two subnets.

I intend to set up a new site in Active Directory into which we shall put any servers/workstations which are on these subnets.

The question I need answered is will I need a domain controller to manage this site?

All I want is to ensure that SCCM does not see or manage assets on the two subnets.

But I know little of the detail about SCCM except that other threads on the internet seem to imply that SCCM may still grab these two subnets?

Not sure if I have explained it very well but all assistance greatly appreciated.

Fuzzier Logic

Viewing all 443 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>