+ Post New Thread
Results 1 to 12 of 12
O/S Deployment Thread, Odd behaviour after OSD completion in Technical; Hi, I've been trying to image a set of Opti 390s and a weird thing happens when the TS has ...
  1. #1
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 23 Times in 15 Posts
    Blog Entries
    1
    Rep Power
    23

    Odd behaviour after OSD completion

    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

  2. #2

    DaveP's Avatar
    Join Date
    Oct 2006
    Location
    Can't talk now: The mother-ship is calling!
    Posts
    9,023
    Thank Post
    352
    Thanked 1,306 Times in 895 Posts
    Blog Entries
    4
    Rep Power
    1133
    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.

  3. #3
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,025
    Thank Post
    43
    Thanked 84 Times in 80 Posts
    Rep Power
    22
    Is it sccm 2012 rtm/sp1/r2

  4. #4
    mrbios's Avatar
    Join Date
    Jun 2007
    Location
    Stroud, Gloucestershire
    Posts
    2,546
    Thank Post
    363
    Thanked 264 Times in 216 Posts
    Rep Power
    101
    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)
    Last edited by mrbios; 30th October 2013 at 08:22 PM.

  5. #5

    Join Date
    Oct 2013
    Posts
    55
    Thank Post
    2
    Thanked 9 Times in 5 Posts
    Rep Power
    3
    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

  6. #6

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,092
    Thank Post
    891
    Thanked 1,742 Times in 1,502 Posts
    Blog Entries
    12
    Rep Power
    456
    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.

  7. #7
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,025
    Thank Post
    43
    Thanked 84 Times in 80 Posts
    Rep Power
    22
    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.

  8. #8

    Join Date
    Jun 2013
    Posts
    49
    Thank Post
    9
    Thanked 8 Times in 7 Posts
    Rep Power
    4
    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

  9. #9
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 23 Times in 15 Posts
    Blog Entries
    1
    Rep Power
    23
    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.

  10. #10

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,092
    Thank Post
    891
    Thanked 1,742 Times in 1,502 Posts
    Blog Entries
    12
    Rep Power
    456
    If you disable startup repair it will fix the trust relationship issue.

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

  11. #11

    witch's Avatar
    Join Date
    Nov 2005
    Location
    Dorset
    Posts
    11,047
    Thank Post
    1,424
    Thanked 2,455 Times in 1,716 Posts
    Rep Power
    717
    Quote Originally Posted by FN-GM View Post
    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

  12. #12

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,092
    Thank Post
    891
    Thanked 1,742 Times in 1,502 Posts
    Blog Entries
    12
    Rep Power
    456
    Quote Originally Posted by witch View Post
    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!

SHARE:
+ Post New Thread

Similar Threads

  1. Odd behaviour with server
    By Edu-IT in forum Windows Server 2008 R2
    Replies: 5
    Last Post: 2nd September 2013, 07:45 AM
  2. [Video] Young Red Panda's Behaviour After Being Surprised... [YouTube: 0:46]
    By DaveP in forum Jokes/Interweb Things
    Replies: 1
    Last Post: 8th January 2013, 09:59 AM
  3. [SCCM 2007] Drive letter of OS Disk after OSD
    By Ric_ in forum O/S Deployment
    Replies: 36
    Last Post: 21st February 2011, 02:54 PM
  4. Odd MRBS behaviour after upgrade
    By Gatt in forum Network and Classroom Management
    Replies: 3
    Last Post: 23rd June 2010, 10:55 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •