Hi Jose,

I've been thinking about a solution to import/export the printer settings. I was thinking on a sort of vbs construction where you export the settings to a regfile and, on logon, import the settings from this regfile with a delay (after pnshell).

Do you have another solution. Is it possible to let pnshell map the printers first and after that import the regkey's.

regards

Sijtze

Hi Jose,

We have the exact same issue.

Our users get a whole lot of printers assigned via Quest. It is too difficult to use policies to set the default so we let the users set their own. However this causes problems as mentioned in this thread.

How would we go about getting a fix for this? The manual idea works but that is not fun at all.

Regards,

Carl

Hi Carl,

I've 'fixed' it using 2 .vbs files. The first one export the two regkey to a two regfiles in the users profile during logoff. The 2 regfiles are than included in the metaprofile. Then using vWorkspace management console I added the second script which runs during logon. This script import the two regfiles in the registry using a delay of 15 second.

This way pnshell first has time to map the printers and after that the personal settings get imported. This is a workaround but it works for us.

What I would like to do is change the way pnshell does it's tasks. In other words I would like to map printers first and after that run script. As you can see when you're running pnshell it first runs added scripts and after that it maps printers.

What the above does is run the printer tasks and then, once the printer tasks are complete, it runs all the other tasks.

If you setup a VBscript as a script task in the vworkspace management console, the script will run after the printers and can inject the settings back in.

Thanks, sounds good. Next week I will give it a shot.

regards

Sijtze

Hi Carl and Sijtze,

I've found a way to get this to work.

You do what Sijtze has done already. Eg, have 2 VBscript. One at logoff that captures the settings and one for login that reapplies the settings.

Then, modify c:\windows\system32\pnshell.cmd

You need to run it twice. The first time run JUST the printer part.

The second time, run EVERYTHING else

It should end up looking like this.

Rem *******************************************************

Rem Added by PMF  to prevent app permissions

Rem from applying to admins

Rem *******************************************************

%windir%\SysWOW64\Ifmember Administrators

If Not ErrorLevel 1 Goto SkipAdmins

%windir%\SysWOW64\pnshell.exe /noapp /noshort /nohost /nocolor /nodrive /noenv /noother /nopol /noprog /noreg /noscript /noshort /notime /nowall

%windir%\SysWOW64\pnshell.exe /noapp /noprint

Goto SkipNonAdmins

:SkipAdmins

%windir%\SysWOW64\pnshell.exe /noapp /noshort /nohost /nocolor /nodrive /noenv /noother /nopol /noprog /noreg /noscript /noshort /notime /nowall

%windir%\SysWOW64\pnshell.exe /noprint

:SkipNonAdmins

Rem *******************************************************

Rem End of script

Rem *******************************************************

Give it a go