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

Unable to connect to WMI (r) on remote machine "SCCMCLIENT03"

$
0
0
Hi!

I'm in the process of configuring the XP firewall to support the Client Push installation method that SCCM offers. At the moment I'm quite happy with the result. The SCCM client agents are installed properly on my reference machines.

To secure that the WMI functionality is up and running I have (prior to the client agent installation) run wbemtest with following parameter (from server to client, and vice versa):

\\host\root\cimv2

I successfully contacted that specific namespace on both ends. But when I trace the log I find the following error which still indicates that something is wrong:

CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Unable to connect to WMI (r) on remote machine "SCCMCLIENT03", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)


Why do I get this? What am I missing here? I got the feeling of WMI functioning the way it should.

Any hints on this one?

In an MSDN-article (http://msdn.microsoft.com/en-us/library/aa389286(VS.85).aspx) I read the following lines:

"If the user account that is on Computer A is not an administrator on Computer B, but the user account has Remote Enable permission on Computer B"

Those lines are part of an article which describes how to configure Remote administrations properly. For that to work, does the computer account of my Central Site Server has to be part of the local administrators group on every client?

Regards,

Fredrik

CCM.log
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 2408 (0x0968)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 2408 (0x0968)
======>Begin Processing request: "TI11WDUE", machine name: "SCCMCLIENT03" SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 1704 (0x06A8)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 1704 (0x06A8)
---> Attempting to connect to administrative share '\\SCCMCLIENT03.spost.nu\admin$' using account 'spost.nu\SA-SCCM_ClientPush' SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 1704 (0x06A8)
Received request: "HPS6133J" for machine name: "SCCMCLIENT02" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 2408 (0x0968)
Stored request "HPS6133J", machine name "SCCMCLIENT02", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 2408 (0x0968)
---> Connected to administrative share on machine SCCMCLIENT03.spost.nu using account 'spost.nu\SA-SCCM_ClientPush' SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 1704 (0x06A8)
---> Attempting to make IPC connection to share <\\SCCMCLIENT03.spost.nu\IPC$> SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 1704 (0x06A8)
---> Searching for SMSClientInstall.* under '\\SCCMCLIENT03.spost.nu\admin$\' SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:13 1704 (0x06A8)
---> System OS version string "5.1.2600" converted to 5,10 SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Service Pack version from machine "SCCMCLIENT03" is 3 SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Unable to connect to WMI (r) on remote machine "SCCMCLIENT03", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Creating \ VerifyingCopying exsistance of destination directory \\SCCMCLIENT03\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Copying client files to \\SCCMCLIENT03\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Copying file "d:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\SCCMCLIENT03\admin$\system32\ccmsetup\MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Copying file "d:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "\\SCCMCLIENT03\admin$\system32\ccmsetup\ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:14 1704 (0x06A8)
---> Created service "ccmsetup" on machine "SCCMCLIENT03". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 1704 (0x06A8)
----- Started a new CCR processing thread. Thread ID is 0xc6c. There are now 2 processing threads SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 2408 (0x0968)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 2408 (0x0968)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 2408 (0x0968)
Found CCR "yb2xbq0a.CCR" in queue "Incoming". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 2408 (0x0968)
======>Begin Processing request: "HPS6133J", machine name: "SCCMCLIENT02" SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 3180 (0x0C6C)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 3180 (0x0C6C)
---> Attempting to connect to administrative share '\\SCCMCLIENT02.spost.nu\admin$' using account 'spost.nu\SA-SCCM_ClientPush' SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 3180 (0x0C6C)
Received request: "YB2XBQ0A" for machine name: "SCCMCLIENT01" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 2408 (0x0968)
Stored request "YB2XBQ0A", machine name "SCCMCLIENT01", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:15 2408 (0x0968)
---> Started service "ccmsetup" on machine "SCCMCLIENT03". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
---> Deleting SMS Client Install Lock File '\\SCCMCLIENT03.spost.nu\admin$\SMSClientInstall.S01' SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
---> Completed request "TI11WDUE", machine name "SCCMCLIENT03". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
Deleted request "TI11WDUE", machine name "SCCMCLIENT03" SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
<======End request: "TI11WDUE", machine name: "SCCMCLIENT03". SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
======>Begin Processing request: "YB2XBQ0A", machine name: "SCCMCLIENT01" SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
---> Attempting to connect to administrative share '\\SCCMCLIENT01.spost.nu\admin$' using account 'spost.nu\SA-SCCM_ClientPush' SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:16 1704 (0x06A8)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2009-03-10 11:12:17 2408 (0x0968)

Where is Toolkit Documentation_x86-en_us.msp?

$
0
0
My attempt to install SCCM 2012 R2 has been stalled when "adksetup" is demanded.  After I downloaded it and run adksetup, it requires 'Toolkit Documentation_x86-en_us.msp" in order to continue the installation.  All searches online have not yielded this documentation.  Why is Microsoft product install so difficult?  Anyone aware where this Toolkit Documentation can be downloaded from, please respond.  Thanks.

EXPORT A LIST OF MACHINES FROM THE DEPLOYMENT STATUS WINDOW

$
0
0

Hi,

 I want to export a details of failed machines error code and error description details for software update deployment from SCCM 2012 Monitoring. Can someone confirm how it is possible, if not possible what is the SQL view for getting the same from SQL database.

Regards,
Madhan

Configuration manager 2007 sp2 component manifest was not found or it was not valid.Configmgr 2007 manifest.cab

$
0
0

I finished installation of my SCCM 2007 Server on (AD/SQL2007R2/SCCM 2007R2 - combined) after so many attempts on separate servers.  I am now facing the issue of configmgr component manifest to continue the configuration.  I searched google for possible resolution and finally found one to download the missing files.  I did and replaced the old one (same as the original one in download folder).  Yet I kept on getting the error. 

The installation completed successfully, but cannot run the configuration manager console.  This is the where I could not continue the set-up

I ran SCCM 2007 update which I downloaded and ran the setup, but it would not connect to the database.  I had to remove it and back to square one.

SCCM 2007 not automatically install updates when deadline expires

$
0
0

Hi

I planned a sccm patching.

Clients downloaded correctly the updates but when deadline expires they not automatically install the updates

Why?

regards

Christian

installation failed with error code 1603

$
0
0

 

Hi all,

 

while installing the configuration manager clients on a system manually, we came across this ERROR:

 

installation failed with error code 1603

 

Do anyone has any idea how can this be resolved. Several posts suggest its a problem related to client push installation method, but since I am installing the configuration manager clients manually, so I mush not be affected by anything related to Client Push Installation. However, be noted that client push installation is well configured on the server, there are certain computers where the client is not getting installed so we are installing the clients MANUALLY to those systems,

 

Any help and suggestions would be higly appreciated.

 

Regards,

Naveed

How to use CCMDELCERT.EXE

$
0
0

Dears,

has anyone tried to use ccmdelcert.exe with SCCM 2007 to change current Duplicated GUIDs on PCs generated in the "Computers that may share the same SMS Unique ID" report...

please explain how?

 

appreciate your assistance

M.Zakaria

SCCM Application Catalog re-direction

$
0
0

HI,

In our SCCM 2012 environment enabled with Application catalog. We wanted to redirect the same with easy remember url. So we created DNS alias name but when we access the URL and try to install applications it give security error. Is there a way to make this work.

Regards,
Madhan


 

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

$
0
0

I installed a new build of SCCM 2012 R2 and I get the following error:

MP Control Manager detected MPsetup has failed to create the CCM_IncomingVirtual Directory

This is my MPSetup logL

<04/27/15 04:28:02>         ======== Installing Pre Reqs for Role SMSMP ========
<04/27/15 04:28:02> Found 2 Pre Reqs for Role SMSMP 
<04/27/15 04:28:02> Pre Req MSXML60 found.
<04/27/15 04:28:02> No versions of MSXML60 are installed.  Would install new MSXML60.
<04/27/15 04:28:02> Enabling MSI logging.  msxml6_x64.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<04/27/15 04:28:02> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi 
<04/27/15 04:28:03> msxml6_x64.msi exited with return code: 0
<04/27/15 04:28:03> msxml6_x64.msi Installation was successful.
<04/27/15 04:28:03> Pre Req SqlNativeClient found.
<04/27/15 04:28:03> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<04/27/15 04:28:03> Pre Req SqlNativeClient is already installed. Skipping it.
<04/27/15 04:28:03>         ======== Completed Installation of Pre Reqs for Role SMSMP ========
<04/27/15 04:28:03> Installing the SMSMP
<04/27/15 04:28:03> Passed OS version check.
<04/27/15 04:28:03> IIS Service is installed.
<04/27/15 04:28:03> No versions of SMSMP are installed.  Installing new SMSMP.
<04/27/15 04:28:03> Enabling MSI logging.  mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<04/27/15 04:28:03> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<04/27/15 04:28:21> mp.msi exited with return code: 1603
<04/27/15 04:28:21> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<04/27/15 04:28:21> Fatal MSI Error - mp.msi could not be installed.

Any ideas why the Mp.msi could not be installed.

Server keeps getting error when receiving first packet - Application has generated an exception that could not be handled.

$
0
0
Im not very clued up in the slightest on this kind of thing, so not sure if this is going to be any help but Im trying to run a server which someone wrote for me which receives information from an arduino ethernet in order to control a game. But every time I run the server I get an error when the server receives its first UDP packet from the Arduino: 

Application has generated an exception that could not be handled.

Process ID=0x215c (8540), Thread ID=0xf9c (3996)

Any ideas what could be causing it? Rob is adamant the code works as he's tested it, so it seems to suggest the issue is on my side.

The source code for the server is on here: https://github.com/cheesestraws/rdip

SMS Site Component Manager failed to install this component on this site system.

$
0
0

Hi,

I'm setting up the SCCM in native mode. All components are in a OK state but the component SMS_MP_CONTROL_MANAGER is in critical. When I look at the alerts there is the following description:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
SMS Site Component Manager faild to install component SMS_MP_CONTROL_MANAGER on server SCCMTEST.

The WebDAV server extension is either not installed or not configured properly.
Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow "All users" read access to "All content". Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" and "Allow Custom Properties" is set to false.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

All requirements are setup according to the links http://technet.microsoft.com/en-us/library/cc872789.aspx and http://technet.microsoft.com/en-us/library/cc431377.aspx. The WebDAV is enabled, the settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" and "Allow Custom Properties" is set to false. I got some messages from the MPSetup.log:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<03-24-2009 16:14:41>  [Allow property queries with infinite depth] should be true (false)
<03-24-2009 16:14:41>  [Allow Custom Properties] should be false (true)
<03-24-2009 16:14:41>  [Allow anonymous property queries] should be true (false)
<03-24-2009 16:14:41>  Allow [All users read access to All content] authoring rule should exist (exist)
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

What should I do? Is there any specific setting in the IIS to be setup? Which log file contain more detailed information?

Thanks in Advance,
Giancarlo

---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account SLKSOFT\scomuser (00000035)_SMS_CLIENT_CONFIG_MANAGER__15576 (0x3CD8)

$
0
0
i am facing this error while pushing clients.
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account SLKSOFT\scomuser (00000035) SMS_CLIENT_CONFIG_MANAGER 5/15/2015 8:42:20 AM 15576 (0x3CD8)

SCCM client installation fail

$
0
0
Hi All,

I have a problem of installing the sccm clinet. below is the ccmsetup.log

Updated security on object C:\WINDOWS\system32\ccmsetup\.    ccmsetup    3/3/2010 3:34:01 PM    680 (0x02A8)
Sending Fallback Status Point message, STATEID='100'.    ccmsetup    3/3/2010 3:34:01 PM    680 (0x02A8)
State message with TopicType 800 and TopicId {BDA28960-FA3F-4598-84A7-FF1CA4B42178} has been sent to the FSP    FSPStateMessage    3/3/2010 3:34:02 PM    680 (0x02A8)
Running as user "SYSTEM"    ccmsetup    3/3/2010 3:34:02 PM    1620 (0x0654)
Detected 89387 MB free disk space on system drive.    ccmsetup    3/3/2010 3:34:02 PM    1620 (0x0654)
DetectWindowsEmbeddedFBWF() Detecting OS Version    ccmsetup    3/3/2010 3:34:02 PM    1620 (0x0654)
Client OS Version is 5.1, Service Pack Version 3    ccmsetup    3/3/2010 3:34:02 PM    1620 (0x0654)
Client OS is not a supported Windows Embedded Platform    ccmsetup    3/3/2010 3:34:02 PM    1620 (0x0654)
Successfully ran BITS check.    ccmsetup    3/3/2010 3:34:05 PM    1620 (0x0654)
IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed.    ccmsetup    3/3/2010 3:34:35 PM    1620 (0x0654)
Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab.    ccmsetup    3/3/2010 3:34:35 PM    1620 (0x0654)
Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml    ccmsetup    3/3/2010 3:34:35 PM    1620 (0x0654)
Successfully loaded ccmsetup manifest file.    ccmsetup    3/3/2010 3:34:35 PM    1620 (0x0654)
Couldn't get directory list for directory 'http://wmr-cmsec-adm.mzd.gahs/CCM_Client/ClientPatch'.  This directory may not exist.    ccmsetup    3/3/2010 3:34:36 PM    1620 (0x0654)
Adding file 'http://wmr-cmsec-adm.mzd.gahs:80/CCM_Client/i386/wimgapi.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\wimgapi.msi'.    ccmsetup    3/3/2010 3:34:36 PM    1620 (0x0654)
Adding file 'http://wmr-cmsec-adm.mzd.gahs:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'.    ccmsetup    3/3/2010 3:34:36 PM    1620 (0x0654)
Couldn't get directory list for directory 'http://wmr-cmsec-adm.mzd.gahs/CCM_Client/i386/00000409'.  This directory may not exist.    ccmsetup    3/3/2010 3:34:36 PM    1620 (0x0654)
Starting BITS download for client deployment files.    ccmsetup    3/3/2010 3:34:36 PM    1620 (0x0654)
Download Update: Connecting to the server.    ccmsetup    3/3/2010 3:34:37 PM    1620 (0x0654)
Successfully completed BITS download for client deployment files.    ccmsetup    3/3/2010 3:35:04 PM    1620 (0x0654)
Successfully downloaded client files via BITS.    ccmsetup    3/3/2010 3:35:07 PM    1620 (0x0654)
Updated security on object C:\WINDOWS\system32\ccmsetup\.    ccmsetup    3/3/2010 3:35:07 PM    1620 (0x0654)
Couldn't verify 'C:\WINDOWS\system32\ccmsetup\wimgapi.msi' authenticode signature without revocation    ccmsetup    3/3/2010 3:35:38 PM    1620 (0x0654)
SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled.    ccmsetup    3/3/2010 3:35:38 PM    1620 (0x0654)
Certificate doesn't have EKU, meaning good for all usages.    ccmsetup    3/3/2010 3:35:38 PM    1620 (0x0654)
IsMSSignedByFileHash Verified file 'C:\WINDOWS\system32\ccmsetup\wimgapi.msi' is MS signed.    ccmsetup    3/3/2010 3:35:38 PM    1620 (0x0654)
Running installation package
  Package:     C:\WINDOWS\system32\ccmsetup\wimgapi.msi
  Log:         C:\WINDOWS\system32\ccmsetup\wimgapi.msi.log
  Properties:  REBOOT=Suppress ALLUSERS=1    ccmsetup    3/3/2010 3:35:38 PM    1620 (0x0654)
Installation failed with error code 1625    ccmsetup    3/3/2010 3:35:39 PM    1620 (0x0654)
Sending Fallback Status Point message, STATEID='311'.    ccmsetup    3/3/2010 3:35:39 PM    1620 (0x0654)

State message with TopicType 800 and TopicId {846B32CA-9F66-400C-851D-EB8D69A6F73E} has been sent to the FSP   
FSPStateMessage    3/3/2010 3:35:39 PM    1620 (0x0654)

The bold is the error im getting.

error code 1625
This installation is forbidden by system policy.  Contact your system administrator.

Source: Windows


there is no group policies to stop the installation.i checked in the OU, Domain group policy & local for windows installer.

Why this client installation is failing?

Sanka

Error code 1603

$
0
0

Trying to download Google Earth, while the install is taking place I get; failed error code 1603. Can someone tell me how to fix or what's wrong.

Client Update Order. Clarify BITS / SCCM Agent / Windows Update Agent

$
0
0
Hello,
first sorry for my bad english. I have a question for "best practice". I have read a lot off stuff, but still some things are not clear.

Environment:
Server 2008 SP2 / Wsus 3.0 SP1 / SCCM 2007 R2 SP2

We are mannaging round about 400 Servers.
The update to SCCM SP2 was done last week. So all Clients have to upgrade to the .2000 SCCM Client.
We also want to update BITS to 3.0 at the Clients. Most of them has a version of 2.5
The Windows Update Agent should be upgraded to 7.4.7600.266. Most of the Clients are running version 7.1.6001.65

So, what is the best practice?

a) Upgrade WSUS to 3.0 SP2
Will this automatic deploy the current Windows Update Agent to the clients via self update? I read this. If so, what about reboot?

b) Deploy current SCCM Agent
Will this also deploy the current Windows Update Agent and Bits? What about reboot?

c) Deploy BITS
I have read that it is sugested to deploy BITS befor upgrading the windows update Agent?

So - all of them need a reboot. And i would minimize this to one. Also we plan a maintanance weekend, where we have to deploy latest Windows Update to all machines.
What will be the best order?

Any sugegstions :-) ???

Thank you, Andre

SCCM Clients are moved to different domain.

$
0
0

Hello,

Can you please let me know what could go wrong with below setup or will it still work without any issues.

Domain A: SCCM 2007 SP2 R2

Domain B: SCCM 2012 


Machines from Domain B will be moved to Domain A and will kept under a OU which are not part of Domain A SCCM discovery.

and the machines which are moved from Domain B to Domain A will continue to report back to Domain B SCCM 2012 server.

Below is some part of "clientlocation.log" of the moved machine where i tried assigning the local site code in vain.

--------------------------------------------------------------------------------------------------------------------------------

Getting Assigned SiteClientLocation5/21/2015 11:41:00 AM4892 (0x131C)
Assigned Site is BMAClientLocation5/21/2015 11:41:00 AM4892 (0x131C)
Getting Assigned SiteClientLocation5/21/2015 11:41:00 AM4892 (0x131C)
Assigned Site is BMAClientLocation5/21/2015 11:41:00 AM4892 (0x131C)
Current AD forest name is dev.bce.ca, domain name is belldev.dev.bce.caClientLocation5/21/2015 12:19:39 PM1204 (0x04B4)
Domain joined client is in IntranetClientLocation5/21/2015 12:19:39 PM1204 (0x04B4)
Rotating assigned management point, new management point [1] is: AGENSM102.corp.ctv.ca (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>ClientLocation5/21/2015 12:19:40 PM1204 (0x04B4)
Assigned MP changed from <AGENSM102.corp.ctv.ca> to <AGENSM102.corp.ctv.ca>.ClientLocation5/21/2015 12:19:40 PM1204 (0x04B4)
Autodiscover SiteClientLocation5/21/2015 4:31:17 PM1672 (0x0688)
Assigning client to site 'PS1'ClientLocation5/21/2015 4:31:31 PM1672 (0x0688)
Unable to verify sitecode 'PS1'. Cannot continue site assignment.ClientLocation5/21/2015 4:31:31 PM1672 (0x0688)
Getting Assigned SiteClientLocation5/21/2015 4:36:32 PM1056 (0x0420)
Assigned Site is BMAClientLocation5/21/2015 4:36:32 PM1056 (0x0420)
Getting Assigned SiteClientLocation5/21/2015 4:36:32 PM1056 (0x0420)
Assigned Site is BMAClientLocation5/21/2015 4:36:32 PM1056 (0x0420)
Assigning client to site 'PS1'ClientLocation5/21/2015 4:43:04 PM5816 (0x16B8)
Unable to verify sitecode 'PS1'. Cannot continue site assignment.ClientLocation5/21/2015 4:43:04 PM5816 (0x16B8)
Getting Assigned SiteClientLocation5/21/2015 4:43:08 PM5816 (0x16B8)
Getting Assigned SiteClientLocation5/21/2015 4:43:08 PM5828 (0x16C4)
Assigned Site is BMAClientLocation5/21/2015 4:43:08 PM5816 (0x16B8)
Assigned Site is BMAClientLocation5/21/2015 4:43:08 PM5828 (0x16C4)
Current AD forest name is dev.bce.ca, domain name is belldev.dev.bce.caClientLocation5/21/2015 4:43:26 PM3720 (0x0E88)
Domain joined client is in IntranetClientLocation5/21/2015 4:43:26 PM3720 (0x0E88)
Current AD forest name is dev.bce.ca, domain name is belldev.dev.bce.caClientLocation5/21/2015 4:44:38 PM2704 (0x0A90)
Domain joined client is in IntranetClientLocation5/21/2015 4:44:38 PM2704 (0x0A90)
Rotating assigned management point, new management point [1] is: AGENSM102.corp.ctv.ca (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>ClientLocation5/21/2015 4:44:38 PM2704 (0x0A90)
Assigned MP changed from <AGENSM102.corp.ctv.ca> to <AGENSM102.corp.ctv.ca>.ClientLocation5/21/2015 4:44:38 PM2704 (0x0A90)
Current AD forest name is dev.bce.ca, domain name is belldev.dev.bce.caClientLocation5/21/2015 4:44:52 PM4900 (0x1324)
Domain joined client is in IntranetClientLocation5/21/2015 4:44:52 PM4900 (0x1324)
Rotating assigned management point, new management point [1] is: AGENSM102.corp.ctv.ca (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>ClientLocation5/21/2015 4:44:52 PM4900 (0x1324)
Assigned MP changed from <AGENSM102.corp.ctv.ca> to <AGENSM102.corp.ctv.ca>.ClientLocation5/21/2015 4:44:52 PM4900 (0x1324)
Getting Assigned SiteClientLocation5/22/2015 1:36:05 PM2800 (0x0AF0)
Assigned Site is BMAClientLocation5/22/2015 1:36:05 PM2800 (0x0AF0)

--------------------------------------------------------------------------------------------------------

Please Advise.

Thank You


The Lightning Khan

Error: Device internal error. Check Schannel, provision certificate, network configuration, device.

$
0
0

Troubleshooing OOB configuration. Each time I attempt to provision an AMT device my amtoplog.log generates a error

 

"Error: Device internal error. Check Schannel, provision certificate, network configuration, device."

 

I've applied the schannel hotfix 942841 to my site server however it doesn't appear to fix the issue. In reviewing the kb article, I noticed that, for my os, Windows 2003 w/SP2 x64, I may need to have 2 files from this hotfix

 

Schannel.dll x64

Wschannel.dll x86

 

I do show the Wschannel.dll in the C:\windows\servicepackfiles\i386 but it's not the latest version. Should I try to find the current x86 version for my x64 system?

AdminUI.WqlQueryEngine.dll fails

$
0
0

Hi,

I am having a problem upgrading the admin UI on primary server to SP1. The upgrade process stops on Register controls Action (InstallUtil.exe keeps on taking up memory, left it for one...) and below is the log from AdminUI.WqlQueryEngine.InstallLog (where the installation hangs).

 

Primary Server is W2003 R2 x64 SP2.

 

Beginning the Install phase of the installation.
See the contents of the log file for the C:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\bin\AdminUI.WqlQueryEngine.dll assembly's progress.
The file is located at C:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\bin\AdminUI.WqlQueryEngine.InstallLog.

An exception occurred during the Install phase.
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Diagnostics.CategoryEntry..ctor(PERF_OBJECT_TYPE perfObject)
   at System.Diagnostics.PerformanceCounterLib.get_CategoryTable()
   at System.Diagnostics.PerformanceCounterLib.CounterExists(String category, String counter, Boolean& categoryExists)
   at System.Diagnostics.PerformanceCounterLib.CounterExists(String machine, String category, String counter)
   at System.Diagnostics.PerformanceCounter.Initialize()
   at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName, Boolean readOnly)
   at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, Boolean readOnly)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryProcessorInstaller.CounterExists(String counterName)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryProcessorInstaller.BuildCounterInstaller(Boolean forUninstallOperation)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryProcessorInstaller.Install(IDictionary stateSaver)
   at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
   at System.Configuration.Install.AssemblyInstaller.Install(IDictionary savedState)
   at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
   at System.Configuration.Install.TransactedInstaller.Install(IDictionary savedState)

The Rollback phase of the installation is beginning.

Any suggestions? Thanks!

Vojta

 

OOB provisioning log warning

$
0
0

During some troubleshooting my OOB client provisioning, I've noticed a warning in my amtopmgr.log that may have a bearing on my issue:

 

"Warning: Currently we don't support mutual auth. Change to TLS server auth mode."

 

My AMT clients are configured with PKI, not TLS - can I safely ignore this warning?

Can load balanced management points be used without registering the service principle name?

$
0
0

I'm about to update our SMS 2003 system to SCCM 2007 and our management points are load balanced.  The guidance says to enable Configuration Manager client approval when the default management point is configured as an NLB cluster, a Service Principal Name (SPN) must be registered in Active Directory Domain Services to enable Kerberos authentication.  In my infrastructure this can only be done by my Active Directory support team, but unfortunatly they will not be able to do this before the upgrade, so I was wondering if this will be a show stopper, or will I be able to continue with the upgrade and use the system and await the SPN to be registered at a later stage?

Viewing all 443 articles
Browse latest View live


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