Borrowing from the title of a recent post by Mr. Revit OpEd I wanted to bring up what I think is a rather critical point to be aware of if you're thinking of running Revit Server on your laptop to solve what is often termed the "Construction Trailer" problem. I've been in touch with the two sets of folks who I know have installed RS on a Win7 computer, that is Mr. Baldachinno and Mr. Cone (Beck / Aaron Maller). For David its an experiment in "low cost" servers for a small company. For Kelly & Co. its an attempt to make an easier way for users in a construction trailer to work on their Central Files.
What I want to highlight is if you're running RS on your laptop, so you can "work" on your central files live over the Construction Trailer's DSL connection with a VPN tunnel, is that your user(s) need to learn how to shut down Revit Server gracefully. The very clear and present danger here is that a user in the trailer, simply turns their computer off, or worse yet, "pulls the plug". I can guarantee that you're playing with fire here if your users do that. There is a good chance that at some point they'll corrupt some or all of the Revit data cached locally to their "server". Autodesk has some clear instructions on how to shut down a Revit Server properly, the problem is, that it involves locking the whole infrastructure while you take down whichever local server you're shutting down. The good news here is that there is a much smaller risk to the data on the actual Central Server. It does a good job of protecting itself and the data it is responsible for, so a Local Server suddenly going off-line should* not affect any of the data at the central server.
Just a word of caution for those attempting to push technology to the bleeding edge and not just the cutting edge.
*Note, I say should, there are conceivably instances where the sudden shutdown of the client or the local server might cause harm to the Central Server data store, but theoretically these should be pretty remote. Worst case is that a lock is left in place on the Central Server due to the "user" disconnecting in the middle of an operation. Keep in mind that when a user SWCs data is committed directly to the Central and Local Servers, and the data is not committed to the project data store until the transaction is 100% verified.