So, $software runs on a 'server' (windows client w/ file sharing to share out the db folder), and laptop client has the drive mapped and $software also installed. This is the vendor's recommended setup.
Well, when user boots up laptop and logs in, wireless isn't connected yet, no mapped drives, so when software is opened it doesn't detect the files (b/c they aren't mapped) and user can't work.
I thought I got around this by using a powershell login script to detect when the wireless connected and then map the drive, but I just followed up and she says the laptop stop working again, so I can only assume that must have broken somehow. The user starts the software manually after logging in, and I'm not going to tell her to go in My Computer and double click the Z drive to manually initiate the mapping, then start the software. Makes me look bad.
What I will be trying when I go onsite is make use of local group policy and
-Set the wireless profile for the office as a computer config, so it logs on before login
-Set the Always wait for network at computer startup and logon group policy
-Use Group policy to set the drive mapping for the user at login
My hope is that all this is done before the desktop appears, because from a user experience standpoint if the desktop is up then everything should be ready to go.
Any other ideas, or things I've overlooked?
Best Answer
If the software supports
UNC paths, you can just use those. You can also add them inNetwork Placesvia Group PolicyUser Configuration \ Preferences \ Shortcuts.Alternatively, you could have the user start the software via a PowerShell script which does the appropriate actions and/or sanity checking before starting the software.