Making BgInfo work in Windows 2012 / Windows 2016

This is the way I make BgInfo work in Windows 2012 (and even Windows 7 too).  It is a little different than in the past but I still need my BgInfo info screen displayed so this is what I figured out.  Follow the steps!

  • You need BgInfo from here.  I recently reused this article with BGInfo v4.21 and now with Windows 2016 too.
  • You should create a c:\utils folder and make sure users have access to it for read and write.
  • This is where things like BgInfo, Autoruns, and Process Explorer would be placed.

utils

  • Next, you will need to create a shortcut to Bginfo.exe.
  • You will need to copy this shortcut to the c:\users\administrator\AppData\Roaming\Microsoft\Windows\Start Menu folder and place it into a new folder called Utilities.  NOTE – if you are doing this as part of template prep you perhaps should use the user folder that you are working as and not administrator – unless of course if you are working as the administrator. BTW, you would do this for things like I mentioned above – Autoruns and Process Explorer.
  • The target should have added to it the existing c:\utils\Bginfo.exe the following c:\utils\normal.bgi so edit the properties of the shortcut.  See below.

utilitieswithparmaeters

  • Create a copy of this shortcut.
  • You will now need to copy it to the Startup folder.

startup

  • You can access the Startup folder at c:\users\administrator\AppData\Microsoft\Start Menu\Programs\Startup or by entering Shell:Startup in the explorer path window.  As you can see below.

startup1

startup2

  • Now you will need to edit the properties of the shortcut in the Startup folder.  You should add /timer:0, to avoid the typical UI popup, /nolicprompt to make sure new users are not prompted to acknowledge the EULA, and /silent to silence any errors.  Not all of these parameters will be seen in the screenshot below.

parameters

Now we have BgInfo configured to be started from the Utilities folder on the Aero desktop, but also to be automatically executed at log in.  But it is not configured for the display that you want.  You should start BgInfo from the Utilities folder – as seen below in the Aero desktop and make sure to save your configuration to c:\utils\normal.bgi.

Aero

Note: this screen above looks different in Win2K16 but it is close enough.  The utilities folder was seen right away, but the utilities in it were not visable for a while and two restarts.  They were functional if you went to their folder but their icon was not seen in the Utilities folder as seen in the screen above.

The configuration of BgInfo when it is working is relatively simple and so I will let you deal with it.  The config I like is seen below.

lookslike

Now you should test.  This will work for the administrator user, plus when you deploy this from template and use sysprep it will make sure that this config is part of the default user and so new users will get it too.

I hope that this helps, and if you have questions or comments please do not hesitate to let me know.

Updates:

  • I have tested this outline with 4.21 of BGinfo and Windows 2016 and it worked – with the comments above.

Michael

=== END ===

Tagged with:
Posted in How To
6 comments on “Making BgInfo work in Windows 2012 / Windows 2016
  1. Michael B says:

    Quick Question – What is the brain damage involved to remove the read only flag from the c:\utils directory? Using the attrib command doesn’t work so well: (run as admin: attrib -r -s c:/utils … unchecking the read only from the folder properties doesn’t work either … e.g. what am I missing 🙂 )

    • Michael B says:

      And this is Win2k12r2 also.

    • Hi Michael B, sounds like you have it. I would have used folder properties. And your run as admin command prompt and do the attrib should have worked. Try log out and log back in, and maybe check the ACL. Sorry no other ideas.

      MIchael

      • Michael B. says:

        Thanks Michael –
        I was admin all the way around, run as admin on the shortcut, new build on the server, not even on the domain yet. Anyway, I ended up running the .exe directly from the c:\utils directory and it wrote the normal.bgi file without issue. One of the lovely things about Microsoft that baffles us and keeps us employed.

        Kind regards,
        Michael B.

  2. Nodorina says:

    Thanks for the instructions.

    RE the normal.bgi, do we create the normal.bgi (by saving the BGinfo.big AS normal.bgi)?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: