Unfortunately not very practical for our users. If I exit explorer.exe and open it again, the entries are gone and I can reconnect the drives. Reconnect and I can't disconnect them with net use /d f: as they are already there for Windows. However, I can't open or disconnect them either. The logon script runs through, but can't remount the drives as they are somehow already there. The other variant is more of a headache for me and I couldn't find a reasonable solution for it yet. Not so handy for users who use shortcuts directly to files/folders on the network drive and can't open them for now. by re-running the logon script (or manually opening the drive). The drives are shown as not connected (red cross), but are immediately connected as soon as I want to open the drive. We run a logon script from Active Directory when logging in (with net use /d and net use /persistent:yes), which works fine with pre-logon apart from two issues: I am testing GlobalProtect pre-logon on Windows 10 and am having problems with network drives. PANW - Press Releases & Public Statements.We are not officially supported by Palo Alto networks, or any of it's employees, however all are welcome to join and help each other on a journey to a more secure tomorrow.ĭo you have support related questions? Check the Support Site Company Information Any help would be much appreciated.This subredditt is for those that administer, support, or want to learn more about Palo Alto Networks firewalls. Our vendor has been unable to resolve the issue. If we cannot resolve this before Monday, we will have move hundreds of files back to an old legacy system to try and be able to open on Monday. It looks like at connect we do not get the: After applying that, I can get 5.2 to load, but not connect. MS released an update for that last year. On the existing workstations which are probably a little older, I could not get 5.2 to load. On later Windows 7 machines it loads and runs flawlessly. Now our vendor is forcing us to connect using 5.2.
The machines were connecting just fine using the previous version of GlobalProtect. This is a short term issue, but it's mission critical. Yes, I know it's Windows 7, but with COVID the new hardware delivery has been delayed yet again.
0 kommentar(er)
