Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows 8 fileserver that is configured to sleep after a period of going unused, and configured to wake-on-lan. I would like to configure some of the Windows 7 systems on the network to map drives from the fileserver. That's easy enough through the standard methods.

The problem is that I while I want the mapping to persist between login sessions, I do not want to wake the fileserver every time someone logs in. I only want it to wake the server if they actually try to access the mapped drive.

When I set the drive to reconnect at logon, the mapping persists, but the fileserver is woken up on every login. If I do not set the drive to reconnect at logon, then the mapping does not persist.

Is there a way to get both of my goals?

share|improve this question
    
Are you able to store the credentials in a script that's visible to the user? You could write a batch or VB script that maps the drive temporarily and opens it, and then create a shortcut to it so it's still just one double click from the desktop or some other location. – trpt4him Nov 22 '12 at 0:09
    
There's no security issue or anything with storing the credentials in a script, but I don't like the extra step that requires. I think I'd rather have the fileserver wake unnecessarily for a cycle than complicate the user interaction that way. – Jeffrey Blake Nov 22 '12 at 5:46
up vote 0 down vote accepted

After a few days it became apparent that not only was the fileserver being awoken each time any computer with a mapped drive booted, but it was also periodically awoken by random traffic from the router. That wasn't acceptable, so I made some adjustments. I ended up adjusting the settings on the fileserver so that it only wakes up in response to a Magic Packet. Then I equipped all workstations on the network with a utility for sending magic packets to the server (you can find a number of these online - I made my own so that it could be a single-click sending operation always directed at the server's MAC address).

So, now the server only wakes when a magic packet is sent. That removes the issue of it awakening every time a system with a mapped drive boots up, and allows the drives to stay mapped permanently (they are just unreachable until the server is awoken).

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .