Sage 100

I have a larger insurance company who is flipping their shit over the thought of physically installing anything on their server. Has anyone installed 2018 to a workstation and then drag/drop the /MAS90 to the server. I know this may work but long term what issues may arise if I don't physically run the install on the server and instead drag/drop the /MAS90 to the server and then share it and have everyone run workstation setup.

What about all the misc Windows folders and registry it writes to during the installation process?

There are dll (library programs) that get registered during the installation. I wouldn't do it.

This is crazy - although I completely get the concern. Apparently this company is running most of their critical applications including Sage off one file server. They are NFW you're setting up a service on this server which then leaves only Standard which they are in return saying ""no way you are running any install on this server"". So they claim that years ago in v440 land someone dragged/dropped /MAS90 onto the server and just ran WKSETUP. Now I think that works (and I used v2017 on a dev environment in pretty much that way to do an interim update) but I don't know what the long-term implications are. I've advised them that if they drag/drop the v2018 program folders that they're probably putting themselves in an unsupported situation regarding Sage. I'm curious if anyone has installed Sage to a local desktop and dragged the \MAS90 to the server and mapped a drive and setup workstations without long term issues. I can't see us going that way because sure as heck someone in three years will walk in and wonder whether this was the first Sage 100 Schulz ever setup because they did it in such an odd way ....

Who on earth goes into a Sage 100 site that's already running the software and even think that there was such a restriction in place and that the customer's response would be that they just dragged and dropped Sage onto the server...... I think I've seen almost everything now.

1. I dont think you will not be able to install patches as it uses the window installer. 2. I believe Standard only uses dlls for the workstation component. 3. IF they don't want a server install, why would they want a client install? 4. I have done it as a work around when having to do an emergency migration to a new server but not with 2018 (There is new encryption of data with 2018 that may be an issue at some future date - Nina will tell you - I try to think of all the possibilities).

You can install on a workstation, then drag it over. Most things work except future patches. Doesn't sound like they will need IM, SO, PO etc. At the point they need the patches installed, copy everything from the server back to the original workstation, install the patches, then copy back to the server. Seems a bit idiotic. Even my medical installs provide access to the server for the initial installation. Hope you have an idiot rate priced accordingly.

@JeffSchwenk I priced them at 250% of what I would have done a similar install since I have dealt with high security IT departments which typically double and triple the effort required. I've advised them to follow with the Sage install guide or they will put themselves into a ""Sage won't support us"" state and I am also not really interested in having another Sage consultant follow me in there wondering why I did such a wonky installation and whether I know how to read an installation guide..... They did all their testing in a fresh development environment which they spun up. The IT folks were shadowing me. It will likely take me about 6 meetings on-site before I can actually install this GLAPAR. FML

In the past, I've installed 100 Std onto NAS devices. Have they considered a hosted solution?

A ""larger insurance company"" should be able to afford another server for MAS on which you could have permission - no?

I'm on more of a need to know basis.... they have other file servers but apparently this one that Sage is on is a pure file storage - no app installs allowed. Surprise!