In theory; it may be possible. Question: "... remote location which will be joined to this production later...." - physical or logical move?
Physical move; in theory it may work ..... OR, perhaps wait until they are physically moved <> deploy the new agent with the proper credentials - granted, this is dependent on how many systems are being moved. Or EEDK the framepkg from the production ePO server <> checkin the newly created EEDK framepkg to the remote ePO server and deploy.
Logical move; will there be a FW between the remote and production? Depending on how far away the remote location is, perhaps setup a Agent Handler w/n DMZ or right behind the FW.
It's a physical move. After the move, will the client register itself with production ePO server?
If you go the virtual route; in theory, it may work. Unfortunately, the only way to test that theory out is to P2V your production ePO (don't forget to P2V your SQL DB if it's separate)
Either of the following can be done fairly simply; pull a system from the remote location <> connect to your production ePO network <> push framepkg with the proper credentials or EEDK the framepkg <> checkin the newly created EEDK framepkg to the remote ePO server and deploy <> bring one of those systems over to your production ePO network and see if they checkin.
It feels like you might have much more luck setting up an Agent Handler in the DMZ at your main site, and then sneakernetting a copy of the Agent around at the new site (or using whatever deployment tool is in place there). It will connect to the Agent Handler over the Internet and you can deploy products that way.