This post is more than 5 years old
26 Posts
0
39531
pnshell not working
I cannot seem to get any shortcuts created. I have run pnshell with the /log /trace switches and this is the result.
Can anyone shed some light on this please.
Thanks
08-Jun-2011 23:48:31 - 3660 : 1612 - CShellConfigFile - Could not open xml file! Xml file name:
08-Jun-2011 23:48:31 - 3660 : 1612 - C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml.old.
08-Jun-2011 23:48:31 - 3660 : 1612 - PNShell.cpp - Reading contents of shell configuration file.
08-Jun-2011 23:48:31 - 3660 : 1612 - CShellConfigFile - Could not open xml file! Xml file name:
08-Jun-2011 23:48:31 - 3660 : 1612 - C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml
08-Jun-2011 23:48:31 - 3660 : 1612 - PNShell.cpp - Waiting on event [PNSHELL_COMPLETE_2]
mselle1
1 Message
1
June 9th, 2011 16:00
It looks like you may have an orphend wallpaper that is assigned to this user. Is this user part of any group/device address/device names/OU that is setup in vWorkspace. If so assign a wallpaper to this group and unassign it. This should get ride of the orphend wallpaper.
Kerry Barnes
26 Posts
0
June 8th, 2011 21:00
Just to add the environemnt is 7.2 MR1, windows 7 64-bit with SP1.
Kerry Barnes
26 Posts
0
June 9th, 2011 06:00
1.That was the out put when run manually.
2.There is no folder "C:\ProgramData\Quest Software\vWorkspace\"
I'll append the switches to the userinit launch and see what happens.
DELL-Andrew W1
378 Posts
0
June 9th, 2011 06:00
Good Morning,
That file should be created when you log into the machine.
Was this an upgrade or a fresh install?
Does the path "C:\ProgramData\Quest Software\vWorkspace\" contain anything?
Normally it'll contain the XML file for the last few Users who have logged in. The new one should be created at login but gets renamed after pnshell finishes with it.
This leads to the question, Is the above log from an actual login attempt or have you generated the file after login by rerunning the process? If it is the 2nd option, we'll need the logs from the actual login instead as this error will just be a redherring.
Thanks, Andrew.
Kerry Barnes
26 Posts
0
June 9th, 2011 06:00
OK. How do I get the pnshell.log from the user login? I have added the /log switch to the usernit launch of pnshell and all I get is a black screen.
DELL-Andrew W1
378 Posts
0
June 9th, 2011 06:00
I was just typing that out for you
ProgramData is a Hidden System folder in Windows 7 so you might have it still but windows is being helpful by hiding it
You might hit an issue turning the log on that way. INstead, open up regedit and go to
HKLM\Software\Provision Networks\Provision-IT
or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Provision Networks\Provision-IT
on 64bit
and create a new String Value called
PNShellLog
Give this a value of the file name and path where your Usr can write the log.
Eg:
C:\log\pnshell.log
Thanks, Andrew.
Kerry Barnes
26 Posts
0
June 9th, 2011 06:00
I can see prgramdata folder alright. I have tried that registry key and nothing seemed to happen. I'll have another go.
Kerry Barnes
26 Posts
0
June 9th, 2011 07:00
In response to the other questions
This is a clean Windows 7 install. Clean 7.2 install and MR1 applied.
Let me see when I directly install the 7.2 MR1 pntools.
DELL-Andrew W1
378 Posts
0
June 9th, 2011 07:00
Make sure you've removed the extra stuff that you added to Userinit.
Edit - too slow sorry
Kerry Barnes
26 Posts
0
June 9th, 2011 07:00
I'm convinced I have seen this before with drives not being mapped. I queried this with Matt Evans but didn't really follow it up.
Strange. RDS works just fine.
DELL-Andrew W1
378 Posts
0
June 9th, 2011 07:00
Well, just finished testing with my Win7 x86 box and it all worked nicely.
My Win7 x64 is being provisioned as we speak so I'll be able to see if it is a generic issue or something in your environment.
Enemy No1 would be a Virus Scanner...
Kerry Barnes
26 Posts
0
June 9th, 2011 07:00
Log working now and the output is below. Still missing that xml file.
09-Jun-2011 08:55:48 - 264 : 1312 - CShellConfigFile - Could not open xml file! Xml file name:
09-Jun-2011 08:55:48 - 264 : 1312 - C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml
09-Jun-2011 08:55:48 - 264 : 1312 - NetworkDriveOperator.cpp - Unable to locate PNShell configuration file. Cannot configure network drives.
09-Jun-2011 08:55:48 - 264 : 1312 - !===========================================================!
09-Jun-2011 08:55:48 - 264 : 1312 - PnShell Log
09-Jun-2011 08:55:48 - 264 : 1312 - User: [AMBERLEA\administrator]
09-Jun-2011 08:55:48 - 264 : 1312 - Operating System Version: [6.1.7601]
09-Jun-2011 08:55:48 - 264 : 1312 - Machine Name: [Remotefx-002.Amberlea.local]
09-Jun-2011 08:55:48 - 264 : 1312 - PnShell Version: [7.2.302.414]
09-Jun-2011 08:55:48 - 264 : 1312 - Parent Process: [pnShell.exe]
09-Jun-2011 08:55:48 - 264 : 1312 - !===========================================================!
09-Jun-2011 08:55:48 - 264 : 1312 - PNShell.cpp - Valid command line arugments found.
09-Jun-2011 08:55:48 - 264 : 1312 - PNShell.cpp - Not running as [SYSTEM] user. Running as [administrator]
09-Jun-2011 08:55:48 - 264 : 1312 - CShellConfigFile - Could not open xml file! Xml file name:
09-Jun-2011 08:55:48 - 264 : 1312 - C:\ProgramData\Quest Software\vWorkspace\ShellResources.xml
DELL-Andrew W1
378 Posts
0
June 9th, 2011 07:00
Yep, works fine on my Win7 x64 so please check for a Virus Scanner causing the issue.
Kerry Barnes
26 Posts
0
June 9th, 2011 07:00
It's the same MSI file. So will be no different.
Kerry Barnes
26 Posts
0
June 9th, 2011 07:00
No virus scanner.
UAC off
Logged in as Domain Admin
Procmon.... seems to try and open the xml file, fails and then closes - as per the pnshell.log.
What creates the xml file in the first place? Does not seem to be in pntools.msi
No policies applied.
All I do is build the VM, initialize and then install pntools. Managed apps assigned to doamin users on the desktop group.