Sage 100

Installing Sage 100 2013 to customer server ( Windows Server 2008 R2) I'm getting: When I run the install it requires several pre-requisites: .NET Framework 3.5 Visual C++ 2005 Runtime LIbraries Visual C++ 1010 Runtime LIbraries While trying to install I get an error: CreateProcess failed for the following command-line: c:\users\wschulz\windows\sysnative\dism.exe /online /enable-feature /FeatureName:NetFx3 My first guess is some type of user rights -- -any others?

Try Antivirus first. I am consistently getting issues (especially with installing Crystal) over the AV. If I temporarily disable it, I can install.

Sounds as if IT had to change something on the server (non-rights related). Now it's installing fine. Although one problem is that it appeared to default to C:\Sage as the install folder. I guess I missed the prompt as to where to install so now I have to uninstall and reinstall to the D:\

I've done that twice! I wish they would make the install path field more obvious (bigger or on its own screen), instead of underneath the modules window.

I'm used to it popping up - also I've found that installing the sample data is usually a requirement or you have problems opening Sage 100 so I have to remember to add ABC data.

I've missed it several times, too!

I have to say on the initial setup Sage Advisor is handy for installing product updates. No more logging to the website, finding, downloading. You can one click and install. Admittedly that ease goes away to some extent when you have enhancements and/or have been using the system for a while and don't trust the auto-update.

#2 pain is the damn Administrator password. Nobody ever remembers theirs. (Note: I'm often not the partner who did their last upgrade). And I know how to reset but it's a nuisance.

Side note: Verified Admin PW reset still works in v2013 PU 2

@WayneSchultz, thanks for mentioning the Sage Advisor on the initial setup for installing updates. It hadn't occurred to me to use it. And I always install ABC company. Although it's a PIA that after you migrate data, you have to go back into Company Maintenance & enter in the company code again.

Does Sage Advisor show on every workstation after you run wksetup? If not then I fail to see what Sage Advisor really is doing for Sage if it's stuck in some server closet. I always turn off the Sage spyware too.

I don't believe it installs as part of wksetup - it's an option on the wksetup menu when you launch the autorun.

From what I remember the updates all have to be server based in 2013 - so even if someone had the notification they wouldn't kick it off from their workstation they'd have to go into the server room. I can't imagine that I'll setup many Sage Advisors on my customer workstations.