[sccm 2012] Odd behaviour after OSD completion

[basicchannel]

Hi,

 

I've been trying to image a set of Opti 390s and a weird thing happens when the TS has finished. You get to the login screen after which I log in with my network creds, only you just get a white sccm 2012 background and a mouse cursor and nothing else; no start bar or desktop icons or anything. Restarting the computer and logging in again seems to solve the problem but I was wondering if anyone else had this problem? I have another restart at the end of the TS but would it be best just to whack in a shutdown -r command?

 

Thanks

 

BC

[6Foot2]

While our stations after building don't behave the way you describe they do seem to require a restart to acquire the customised logon screen we have specified.

 

I think that, perhaps, if we gave the stations enough time they might restart anyway.

 

We haven't found this out yet as it has always been a rush to get the computers working since deploying SCCM 2012.

[free780]

Is it sccm 2012 rtm/sp1/r2

[mrbios]

Checked the smsts.log file to see what it's trying to do while it's stuck on the SCCM background?

 

Might be worth popping that into cmtrace and seeing if something is getting stuck.

 

EDIT: or upload the log and i'll take a look for you if you like, i've gotten pretty good at working through the logs these past few days (and now my SCCM 2012R2 server is running schweeeeet)

 

EDIT: actually what you're experiencing isn't what i thought (given that you get a login box)

Edited October 30, 2013 by mrbios

[Techie-v2]

We always get the grey sccm backgroubd after a build until the machine has been restarted. Get the taskbar and start menu though. Though nothing of it really. Putting a restart at the end of the task sequence doesnt seem to make a difference

[FN-GM]

Yep same as us apart from the machine is usable unlike @basicchannel . Also the custom login screen background does not apply until the machine is rebooted (Windows 7). Also the same as @Techie-v2 a reboot in the TS doesn't work. It also happens to the bank i worked for, using SCCM 2007. It will be probably widespread.

 

In all honesty i have never looked into it.

[free780]

I just get it pause on 2012 r2. Then it goes to the logon screen. It reminds me of mdt which will sit there at the enf of a ts while the logs are copied.

[timtom]

GP processing is disabled during SCCM's build so you need a final reboot to get it to pick up the changes. I looked into this a while back and the only successful way seems to be adding a custom registry entry that waits x seconds after the build finishes and then does a one-off reboot. Needless to say I didn't worry about it, background processing triggers after an hour for us so and none of the workstation policies are critical

[basicchannel]

Hi ALl,

 

Sorry been away from Edugeek. I'm not too worried at the moment because a restart seems to fix the problem, but I'm not happy with these Optiplex 390s. I'm now getting reoccurring broken trust relationship problems and they're just generally sh*te. I'll check out the SMSTS log and see what I can dig up. Maybe a graphics card issue or something.

[FN-GM]

If you disable startup repair it will fix the trust relationship issue.

 

bcdedit /set {default} recoveryenabled No
bcdedit /set {default} bootstatuspolicy ignoreallfailures

[witch]

If you disable startup repair it will fix the trust relationship issue.

]

Mostly...I have it disabled in both schools and I still get the odd one reoccuring - but it does a pretty good job on the whole

[FN-GM]

Mostly...I have it disabled in both schools and I still get the odd one reoccuring - but it does a pretty good job on the whole

 

We never used to have it, but after converting loads of machines to x64 it popped up a little. Its strange. XP never did it!