Snazzy OSD status with BGInfo

re: Snazzy OSD status with BGInfo

martian — Sun, 10 May 2009 23:55:48 GMT

I saw you-guys at MMS. Great presentation. I have implemented this "snazzy" tip as much as I can. My manager likes your graphics better than the one that I am using. Can you post the STEP_##.bmp files? Also, is there any reason why you can't make the utility to hide FirstUXWnd available for download? It would be a big help.

I'm looking forward to more of your great posts. Keep up the good work.

Thanks

re: Snazzy OSD status with BGInfo

cmse — Tue, 12 May 2009 00:43:11 GMT

Martian:

We appreciate the compliment and glad you could make it! We will absolutely help you out and will do a quick post today that shows our source for doing the hide and will share the bitmaps with you in bland format. We have to be certain to strip out any references to Microsoft so you will only get the progress bar piece and we hope that is cool! We have it on the radar for today...

Thanks

-Chris

re: Snazzy OSD status with BGInfo

cmse — Tue, 12 May 2009 10:44:58 GMT

Martian:

Here is a full-source example for hiding FirstUXWnd. I hope this helps:

http://blogs.technet.com/osd/archive/2009/05/12/c-sample-hide-window.aspx

-Mike

re: Snazzy OSD status with BGInfo

jeremy_decker@valleymed.org — Wed, 20 May 2009 20:37:56 GMT

I think im missing something with my setup of this, i created my .bmp, I setup BGinfo and seperate config files for each back ground. I then updated my boot image to contain the first back ground, and added my package to the DP. In the task sequence i used run command line and used step.bat X for each time i add it to the sequence. My problem im having is that when it refreshes for a second time i am only getting the background color and not the BMP loading. Is there a cache i need to clear in between refreshes? also after the reboot it doesnt pull the new BGinfo package for awhile so it is sitting at my default screen and not at the installing windows screen.

re: Snazzy OSD status with BGInfo

cmse — Wed, 27 May 2009 00:22:02 GMT

Can you be more specific about "refreshes for a second time"? Is it (initially) setting the background properly, but losing it later?

As for the second part of your problem, a reboot will reset wallpaper back to the WinPE default. Make sure to place a BG step after any reboots.

Now, if this is during the "Setup Windows & Config Manager" step, read on… You "lose" control of the Task Sequence (and background) from the time the new OS boots (post-WIM install), until after Setup Windows & Config completes. During this time the new OS is booting for the first time with its out-of-box background, running OSD hooks, and installing Configuration Manager on the new OS. Once this is complete, task sequence control resumes. I place a BG step immediately after this step, and hide the FirstUXWnd screen.

I hope this helps -

Mike

re: Snazzy OSD status with BGInfo

hamil998 — Sun, 31 May 2009 00:01:27 GMT

Hi Mike,

What do you for the image load phase (unattend) when the background changes and the TS is not able to run a bginfo? Is there a way to change the setup background somehow?

re: Snazzy OSD status with BGInfo

cmse — Thu, 04 Jun 2009 00:21:04 GMT

I leave first boot (unattend) alone. Thankfully the time spent here is short; TS hooks resume control soon afterwards.

Changing the initial boot background image is probably possible, but I imagine it’s more trouble than it’s worth. When weighing the risk vs. benefit, it doesn’t seem very appealing.

Just thinking out loud, but perhaps it would entail something like:

1. Install the WIM; while in PE, somehow install an OS hook on first boot and reboot

2. On first-boot, hook will trigger; set BG and hide FirstUXWnd

It's the "hooking" part that introduces a risky unknown at this point.

re: Snazzy OSD status with BGInfo

Thomas — Wed, 08 Jul 2009 16:20:43 GMT

Have anybody made this work with MDT 2010 Beta 2?

re: Snazzy OSD status with BGInfo

Mike N. — Wed, 15 Jul 2009 15:13:52 GMT

I don't see where the BMP files were ever posted online. Am I just missing them somewhere? Or, if I do have to make my own, what resolution should they be?

re: Snazzy OSD status with BGInfo

cmse — Thu, 23 Jul 2009 23:45:54 GMT

Hi Mike N.,

If you are a member of our Connect program (connect.microsoft.com) then you have access to the ModenaOSDTools.exe that has several Zip files that are extracted.

In the Scripts.zip, there is a folder called Scripts\BG that actually has BGINFO.exe and our sample BMP files along with WindowsHide.exe.

You can alter these as you see fit!

Thanks,

-Chris

re: Snazzy OSD status with BGInfo

cmse — Thu, 23 Jul 2009 23:48:10 GMT

Hey Thomas,

I don't believe that anyone on our end (Microsoft) has tested with the MDT toolkit. We don't use the toolkit as we have to stay closer to release time where MDT is usually 90+ days after the releases. Thus, we don't have it in our scope.

You could ask the deployment guys via there blog http://blogs.technet.com/deploymentguys/ as they are the ones that would probably have tested the use of our wizard with their tools.

Sorry we haven't had time to test this but hopefully this helps just a bit...

Thanks,

-Chris

re: Snazzy OSD status with BGInfo

Vitalie Ciobanu — Fri, 14 Aug 2009 13:57:29 GMT

Hi guys!

Thanks for this, works great! Except one thing :)

It seems I can't make the bmp image dissapear after TS has finished. While the user is displayed with ctrl+alt+del dialog box, it has the last bmp background.

How can I stop it from displaying after TS has finished successfuly?

Thanks,

Vit