[Client Installation from OSD]

Configuration manager client program requirements by default does not include the platform for windows 7 (X86 or X64), just you need to add them.

[The task sequence can not be created]

I install SCCM Sp1 and after that upgrade to SP2

when try to create task sequence I have the following error

 

 

Error: The task sequence can not be created. Please see following error information or log file to resolve the issue.

 

- An error occurred when storing the task sequence.

 

Error: Create a New Task Sequence

 

 

And when try to open the log files for task sequence like Smsts.log,TaskSequenceProvider.log and CreateTSMedia.log

 

and i don't get any useful way to troubleshoot this problem

 

The log i found

[8][12/8/2009 AM] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe ConfigMgr Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)

at Microsoft.ConfigurationManagement.AdminConsole.OsdCommon.OsdUtilities.SetSequence(ConnectionManagerBase connectionManager, IResultObject taskSequencePackage, IResultObject taskSequence)\r\nConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

Description = "Failed to call SMS_TaskSequence::SaveToXml due to error 80041013.";

ErrorCode = 1078462229;

File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";

Line = 2932;

Operation = "ExecMethod";

ParameterInfo = "SMS_TaskSequencePackage";

ProviderName = "WinMgmt";

StatusCode = 2147749889;

};

\r\nSystem.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:

instance of SMS_ExtendedStatus

{

Description = "Failed to call SMS_TaskSequence::SaveToXml due to error 80041013.";

ErrorCode = 1078462229;

File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";

Line = 2932;

Operation = "ExecMethod";

ParameterInfo = "SMS_TaskSequencePackage";

ProviderName = "WinMgmt";

StatusCode = 2147749889;

};

\r\n

 

 

 

 

Please can anyone advice me.

[How does SCCM handle PC name changes on a client?]

This case not in my environment but it usually happen to me in SMS 2003

 

My question is how the SCCM handle this

[How does SCCM handle PC name changes on a client?]

Hi.

 

How does SCCM handle PC name changes on a client?

 

when changed the name of a test machine. I found both name old and new one. However, the old name said it had the client installed, but the new name did not have the client installed.

 

Is there a way configure or repair the client to be enabled and installed on the PC/?