sysprep unable to change admin password

wds, mdt2010, windows xp

Using wds and lite touch i was getting the following error after syspreping my machines: setup was unable to change the password for user account administrator


Basically I built the image before hand and I had the admin password coded in the image. For some reason it didnt like this. I tried several ways and the only fix I found was to recreate my image without having an admin password. Basically i reset the password to blank..

From there after booting to lite touch and imaging, after it reboots it goes through with changing the admin password. I also have encrypted the password in my sysprep.inf. I read somewhere that encryption was causeing the error but tried both ways.


summary: create admin account with no password before sysprep.

Number=9 Description=Subscript out of range Source=SMSComponent

Was getting the following error in smsreporting.log on my sccm 2007 server.

Number=9 Description=Subscript out of range Source=SMSComponent

From there I found a few answeres but it seems to be ASP Buffer Limit in IIS. The default is 4mb and changing that seems to be the fix for that error.

I'm going a little further as I'm turning off the buffering and going to keep an eye on things. Yikes! Plus if I just fix things there will be nothing to post here. :)

SCCM 2007 Advertisements Do Not Show In Run Advertised Programs

OK now maybe I missed something in the manual (wait I skipped the whole thing) but for the last couple hours I've been creating packages and advertisements and they do not show up in the control panel under run advertised programs..

I came across a post that said ''By default, mandatory programs don't appear in Run Advertised Programs.''

HAH that was it. I was setting mine all to mandatory so they would install and I could read the logs to see if it worked.. Silly me

SCCM 2007 Unable to locate Remote Assistance files

Server 2008 - SCCM 2007 sp1

Right clicking on a system and picking the Remote Assistance option I got the message “Unable to locate Remote Assistance files.”

To fix:

Goto Server Manager and scroll down to Features. Click Add Feature. Look for Remote Assistance and check it to be installed. Clicking Next, install and finish

Should be it. Try to assist again.

MP has rejected a policy request

MP has rejected a policy request from GUID:12345-1234-1234-1234-123345678 because it was not approved. The operating system reported error 2147942405: Access is denied.

I was getting quite a few of the above errors. I didn't know where the machines were so I had to run a query to find the Names of the problem computers. Heres what I used:

select
resourceID, netbios_name0, SMS_Unique_Identifier0
from
dbo.v_R_System
where
(SMS_Unique_Identifier0 = 'GUID:YOUR GUID FROM THE ERROR')


this returns the name and you can follow up and fix the problem :)

Failed to install SMS client The error code is 80041002

ccmsetup.log showed

Setup failed due to unexpected circumstances. The error code is 80041002

also in client.msi.log the following error was there as well

Product: Configuration Manager Client -- Installation operation failed.

seems there are lots of different causes and fixes. Here is the one that fixed this for me.

1. Stop the "Windows Management Instrumentation" service.
2. Rename the %WinDir%\System32\Wbem\Repository folder to ”Oldrepository”.
3. Restart the “Windows Management Instrumentation service”.
4. Verify that the %WinDir%\System32\Wbem\Repository folder has been recreated.
5. Reinstall the SMS client software.


**Update**

Seems I randomly would get different message's so I checked my rights on the shared folder that the client is in. I gave everyone read and execute and so far so good on the installs

Input Box To Change SMS Site Name By Computer Name

Here is a little script that I put together by combining a few other scripts. When ran an Input box will pop up and ask for the computer name. It will then return the current Site name, then the new name that you specify by editing the file. If the computer is not on nothing will be returned.


Option Explicit
On Error Resume Next
Dim WSHShell, WSHNetwork, Input, smsClient, inparam, Newresult, Newsite, oCCMNamespace, strComputer, result

Set WSHShell = CreateObject("WScript.Shell")
Set WSHNetwork = CreateObject("WScript.Network")

Input = InputBox("Enter the Computer name","SMS Site Code Fix")
strComputer = Input

'get the current site code
set oCCMNamespace = GetObject("winmgmts://" & strComputer & "/root/ccm")
Set smsClient = oCCMNamespace.Get("SMS_Client")
Set result = smsClient.ExecMethod_("GetAssignedSite")
wscript.echo strComputer & " Current Assigned Site is: " & result.sSiteCode

'Reassign the site code
Set inParam =smsClient.Methods_.Item("SetAssignedSite").inParameters.SpawnInstance_()
inParam.sSiteCode = "XYZ"
Set Newresult = smsClient.ExecMethod_("SetAssignedSite", inParam)
Set NewSite = smsClient.ExecMethod_("GetAssignedSite")
wscript.echo strComputer & " New Assigned Site is : " & NewSite.sSiteCode


Make sure to change the site code to your site code.
inParam.sSiteCode = "XYZ"

Logon Script to change SMS Site Code

Found this script and it seems to do the job. I've added it to the logon script in AD

sSiteCode = "XYZ"
sMachine = "."
set oCCMNamespace = GetObject("winmgmts://" & sMachine & "/root/ccm")
Set oInstance = oCCMNamespace.Get("SMS_Client")
set oParams = oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
oParams.sSiteCode = sSiteCode
oCCMNamespace.ExecMethod "SMS_Client", "SetAssignedSite", oParams

change xyz to your sitecode

This task sequence cannot be run because the program files for "package" are inaccessible on the distribution point

For me my password was spelled wrong and It couldn't connect to the SCCM server. To resolve this issue, you must correctly configure the System Center Configuration Manager 2007 client network access account. To do this, follow these steps:

1.Use an account that has administrative permissions to log on to a computer that has the System Center Configuration Manager 2007 Administrator Console installed.
2.Click Start, click All Programs, click Systems Management Server, and then click SMS Administrator Console.
3.Expand ServerName, expand Site Management, expand SiteName, and then expand Site Settings.
4.Click Client Agents, right-click Computer Client Agent, and then click Properties.
5.In the Computer Client Agent Properties dialog box, next to the network access account that you want to configure, click Set.
6.In the Windows User Account dialog box, enter the user name and the password that you want to use for the network access account, and then click OK two times.

SQL databse suspect

Well a power outage today killed my SQL database. Seems the database was in suspect mode. I got tons of errors. Logs pointed towards SQL so I tried the following:

EXEC sp_resetstatus ‘DBname’;
go
ALTER DATABASE DBname SET EMERGENCY
go
DBCC checkdb(’DBname’)
go
ALTER DATABASE DBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
go
DBCC CheckDB (’DBname’, REPAIR_ALLOW_DATA_LOSS)
go
ALTER DATABASE DBname SET MULTI_USER
go

I ran that in sql server management studio as a query. It fixed alot of errors but still had alot. I ended up running the SCCM 2007 disk again and picked to reconfigure the SQL section. Now my console is back up and running. Must warn you that the above can lose data if it can't be recovered.

Windows 7 RC with SCCM console, Endpoint

Well I'm trying to load most of the stuff I have on my xp box. So far I have loaded the SCCM 2007 console without any problems and also symantec Endpoint. Now Endpoint windows 7 didn't like very much. I bypassed or accepted all the errors and are you sure windows by choosing yes or ok. It has installed fine and I've actually managed it to my SEPM Server. It grabbed the updates from it as well. It doesn't report to Windows 7 very well as it states my definitions are wrong yet they are one day old. More Screenshots yay!!!

Seems Endpoint reports to Windows Security is no longer supported. They recommend Some of the other brands. Norton's is listed so this is probably too early as Endpoint is newer then Nortons as far as I know. I would think they'd use the same technology but who knows.

Assigning Advanced Clients from the Command Prompt

I've found this and it may useful to some people.

Assigning Advanced Clients from the Command Prompt
You can assign Advanced Clients to SMS sites by running a script at the command prompt. The Advanced Client has a scripting object (Microsoft.SMS.Client) that you can use to do this. This object is installed with the Advanced Client software. For more information, see the Microsoft Systems Management Server 2003 Software Development Kit.

The following example demonstrates several of the Advanced Client scripting methods.

Set smsclient = CreateObject("Microsoft.SMS.Client")
oldsite = smsclient.GetAssignedSite
wscript.echo oldsite
smsclient.EnableAutoAssignment(True)
'or:
smsclient.SetAssignedSite("NES")
Adjust the script as necessary for your specific requirements.

SCCM 2007 Deploying Packages

Hmm now this is really starting to bug me. I've basically setup packages and advertisements just about every which way I can think of plus various ways from various sites. The packages never report to SCCM that it was a success. When logging into clients I'd get the New Programs Installed and the software does indeed work. On the clients in windows\system32\ccm\logs opening execmgr.log I see several messages. What I do notice is that my clients report with a status code of 0 and it states success.

So if your also having this issue make sure to check your logs on the client cause it actually may be installed. The programs I'm talking about mostly are Adobe flash, reader, shockwave, java. They all install successful but sccm reports program errors or failures.

Anyone that got successful returns in SCCM feel free to comment.

SUP Role In SCCM 2007 Sync Error

Ok now maybe I over looked some steps but I have gone back and forth with tons of trys/fixes and I think I finally found the answer. My site is setup like this: Already in place WSUS and a new SCCM2007 server. Here is what I have found and it seems like that is how I was trying to set it up

Server 1 (SCCM) is the server server with WSUS admin console

Server 2 (WSUS) is the WSUS server

On WSUS, add SCCM as a local admin (don't need to do anything else)

On SCCM, ADD a NEW server:

* Name is WSUS

* Specify the WSUS server FQDN

* The only role is SUP

* Make it an active SUP

* Sync with Microsoft Update

* Set the rest of the parameters as desired


So It seems I was trying to add the role to my site server instead of the WSUS server. I never thought to add another server under the site systems. ::Slaps face::
Anyway I'm checking my log file now and its at 96% synching!! woo hoo!

SCCM 2007 Tool Kit

I've found the link for the 2007 toolkit. You can download it from the following link:

SCCM 2007 Toolkit Download

Configuration Management Console Lacks All the Views

Well I was trying to configure a MMC with just certain objects such as just the computer management section. It runs a little wizard and you pick custom and you can select which options you want to show. That part worked but I tried to set it back and no matter what I picked it kept the same options with just the computer settings part.

I basically copied the adminconsole.msc from the install source in SMSSETUP\AdminUI\bin to Drive:\Program Files\Microsoft Configuration Manager\AdminUI\bin

Then I ran my Console and all the settings were back in place. Not sure why re-running the wizard and selecting all the tree didn't fix it.

Another fix is to make a new MMC and add the System Center Configuration Manager Snap-in.

Installing SCCM 2007

OK i've found a pretty good forum with help on installing and confiuguration of SCCM 2007 on Server 2008 / 2003. Also Has alot of Info on errors, other installs, and just about anything else you could think of to help. So check it out, wont be needing my help since this site has it all :( hehe

SMS, SMS 2007

Installing IIS on server 2003 for SMS

Well found a good link for the correct way to install IIS for SMS on windows server 2003. Follow the link.

Installing IIS

DMP not responding to http error 12152

the following error appeared after a reinstall pf my MP.

MP Control Manager detected DMP is not reponding to HTTP requests. The http error is 12152.

Well This error has to do with Devices. Seems I'm not using this to monitor mobile devices so I haven't found a fix yet and just unistalled the role. I did try and clear it up but no luck as of yet.

I did eventually run across this site with steps to install DMP but I haven't tried. here's the link for that incase you want to give it a whirl.

DMP Step By Step Guide

mp.msi exited with return code: 1603

While installing the MP role on SCCM 2007 my MPsetup.log file showed me the mp.msi exited with return code: 1603 error message. The following fixed that error and my MP installed successfully the next try.

BITS is not installed with IIS. Goto

add/remove programs > add/remove windows components > application Server (click details) > Internet Information Services (Click Details) > *CHECK* Background Intelligent Transfer Service[BITS] Server Extentions

Make sure it checks both options under the details of BITS. Click oks and after the install try installing the MP role again and it should be successful.