Friday, January 18, 2013

Restricted users can only print blank pages

Problem: restricted users can only print blank pages. Both printing and print preview produce blank pages to local printers.

Solution: found here.

Firstly, the ‘Low’ folder mentioned above is needed as a temporary working folder for the HTML pages being generated and printed from IE. Start by bringing up a command prompt (run -> cmd), making sure you DO NOT run with elevated permissions (otherwise it will do this for your local admin account, which won’t help you). At the command prompt, run the following command:
mkdir %userprofile%\AppData\Local\Temp\Low
This will create the necessary Low folder in the right place, which is almost certainly absent otherwise.
Other posts I read suggested this was enough, but it isn’t. The newly created ‘Low’ folder won’t work until you run a further command which sets the integrity level of this folder such that IE can use it (IE7 introduced a new protected mode, which you can read more about here: So at the same prompt, run the following command:
icacls %userprofile%\AppData\Local\Temp\Low /setintegritylevel low
Having done this, restart IE, and you should find print preview and printing itself now works

Thursday, January 3, 2013

Deploying IE9, shortcuts don't work for non-admins on first login

Problem: After deployment of IE9, the IE9 shortcuts don't work for non-admins until IE9 is launched by a local machine admin.

Solution: found here;

Thank you Adam2608!

Basically, there is a command in the RunOnce registry key that needs to be run by an admin to finish off the install.
That command is:
 reg.exe DELETE "HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components" /v "NoIE4StubProcessing" /f

We've put that in a script and set it to run at machine startup. Running it at startup ensures it runs as the local system account in case you restrict registry tools (we do, as we are a school).
Onces thats run, anybody who logs on gets the icons.

Update 5/30/13: Another option I've found is to use the IEAK for IE9 and build your own custom installer for IE9. This works better for SCCM Build and Capture task sequences and will probably work better for distributing IE9 after the machines have been deployed.

SCCM Adobe Acrobat Pro deployment failed with error: 80091007

Problem: Failed to run the last action: Install Adobe Acrobat Pro 9. Execution of task sequence failed. The hash value is not correct. (Error: 80091007; Source: Windows)

This error is happening with all my Build and Captures in SCCM 2007 R3 that include Adobe Acrobat Pro 9. After all the fiddling with settings, hash checking, removing hidden files, nothing would fix it!

By the way, the package would install perfectly if deployed via advertisement in windows, just not in my Task Sequences.

Solution: In the Advertisement for the build and capture, on the Distribution Points tab, change from "download content locally when needed by running task sequence", to "Access content directly from a distribution point when needed by the running task sequence".

This not only solved the issue with Acrobat, but the build and capture took about 50% less time, as windows and other packages didn't need to download. Excellent!