You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't believe a logoff script is triggering for users that have been created by pGina.fork. The log shows it trying to find a profile and uncompress it, but since no .wim file has been saved yet, it doesn't find one. When it logs off, I don't see any indication in the log that a logoff event has triggered the script to compress the profile, and/or move it to the fileshare. Am I missing someting? Thanks.
The text was updated successfully, but these errors were encountered:
Adding for clarity. I'm testing on a Windows 10 VM but I've also got a trio of Windows 10 desktops ready to go, if I can get the centralized profile thing going :) I started with pGina, but moved to this fork when I discovered pgSMB2. Seems like EVERYTHING is working except for the script to create the profile backup (I was able to run it manually, I'm using imagex.exe with your imagexEX wrapper. I did notice that the log showed all of the %u substitutions when it reported the values for the script lines, but it DIDN'T substitute the profile folder for %z, so I changed it in the plugin config to c:\users%u, which did clear up the way it displayed in the log, but I still don't see anything triggering. It doesn't create the archive, and even when I manually created the archive, it doesn't move it to the fileserver. Hope this helps, as I know my original description was a bit vague.
I don't believe a logoff script is triggering for users that have been created by pGina.fork. The log shows it trying to find a profile and uncompress it, but since no .wim file has been saved yet, it doesn't find one. When it logs off, I don't see any indication in the log that a logoff event has triggered the script to compress the profile, and/or move it to the fileshare. Am I missing someting? Thanks.
The text was updated successfully, but these errors were encountered: