The problem - beyond just having a license - is getting pro to work outside of your company enviroment. You need to do a completely new config.pro (and swap it out before staring up pro) to map to your local drive rather than network drives. You need access to all the files that are on your network - especially library files and piece parts of any assembly you are working on. Copy them all to your local drive before leaving work. Then pro still seems to take forever to start, but will work once running. If someone got tricky with the config.pro, you may have additional problems running remotely (missing files you didn't know about...). I have tried to work via cisco VPN, with zero luck. Pro will start after about 10 minutes of waiting, but it will not load up any models from the (vpn) network. Well, that's not exactly true - they do load, but the network traffic is in bits/sec that doesn't even register on the meter - so I'm guessing after a few days it may actually load a simple assembly. Your network may not have this issue - but mine does. I would check this out before sending someone out of town expecting to have pro access.