Improve this question. Jeremy Jeremy 3 3 gold badges 11 11 silver badges 16 16 bronze badges. Any particular reason why the XP machine can't be joined to the domain? That would seem to be the most obvious solution. There is a reason, though one could debate whether it was a good reason. Add a comment. Active Oldest Votes.
Joining the domain is the best answer. The following works but isn't secure. Reboot the workstation and test again. Improve this answer. Ed Fries Ed Fries 1, 2 2 gold badges 11 11 silver badges 13 13 bronze badges.
I use a. Good idea. One small wrinkle I have is that sometimes this machine needs to connect to the share over a VPN, so the share is not actually available until then. Maybe a shortcut or something on the desktop to remap? I will try this if I cannot get it onto the domain. Try adding the credentials as stored credentials if there are none listed. It worked for me.
Chris Chris 11 1 1 bronze badge. Dave M Dave M 4, 21 21 gold badges 29 29 silver badges 30 30 bronze badges. XP machine ain't on the domain so this would be the local policy only. Are thre stored credentials that no longer match account info. Maximus Minimus Maximus Minimus 8, 1 1 gold badge 21 21 silver badges 35 35 bronze badges.
If that makes sense.. I might try this Local Policy setting - I have used this for software deployment via GP in the past to good success.
If you want to turn off password protected sharing you need to ensure the guest account is enabled on both boxes as this is what it will use, by default it tends to be disabled. I don't think I enabled the Guest account on either when I turned off password protected sharing - I would like to try this, but it will still create a second user account that is visible on login to the user on the Win 7 machine which is something we was trying to avoid if possible.
With regards to the Everyone group, I think I gave Full control on the folder permission and likewise, or owner on the share permissions.
I am not sure our RemoteApp configuration is working correctly. If the Win XP machine is not logged on, then the application launches as expected but if there is someone logged into this machine, the Win 7 user has to expand the RemoteApp window, and choose to disconnect the user currently logged on. From the Win XP perspective, the user currently logged on receives a message stating that another us trying to access this computer and the can accept or reject the connection.
Am I right in thinking that if there is no response after a certain time period it will automatically disconnect the session on the Win XP machine? I suppose my question - is there a way to force this disconnection immediately as soon as RemoteApp is launched. If you can, w have just had a thought, what about using the auto-sign on feature on the Win XP machine and the drive should then get mapped before it is needed. You could force the session to disconnect when you close the remoteapp but I'm not sure this is what you need Also which is the host of the remoteapp in this scenario XP or 7 and are both of these machines in use locally or is one acting as a 'server'?
Forcing the session to disconnect when I close RemoteApp would be different to forcing the user to log off the Windows XP machine. That GP setting 'Set time limit.. Is the user just logged onto the XP machine via remoteapp ie. Does closing the remoteapp leave the user with a logged on remote session on the XP box? Just trying to build a picture :.
If we want the network drive mapped on Win XP machine , at the moment this happens on logon and therefore a session would be open and running on the Windows XP machine. If the RemoteApp is launched, it will not run successfully unless the user expands the RemoteApp window and chooses to disconnect the user and waits for a certain period of time, until it times out at which point it should disconnect the session on the Windows XP machine and the RemoteApp should launch.
In typing this out.. I've thought of another issue The penny has dropped! I understand now and I hate to be the bearer of bad news but I don't think you can do what you are trying to achieve. As you say you can't have the mapped drive without being logged on and if you log on that is going to lock open your one available session. The cheeky patch for multi sessions hasn't worked for a while, I remeber trying it in the past, also I think the mapped drive would be session specific, although that might not matter for your purposes.
Can you not configure your remoteapp to use a UNC path instead of a mapped drive, then we're back to ensuring the correct permissions are on the final path? To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.
Best Answer. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:.
Last reply by Hydralisk Unsolved. Mapped Network Drives - Remembering the Password. What I experienced: 1. I found I had access to these drives, with no problem, during the Windows session.
My issue: I do not want to have to re-enter the username and password to access the drive, should I restart the machine. All forum topics Previous Topic Next Topic.
Replies 6. Hydralisk 5 Tungsten.
0コメント