Sage 100

Anybody familiar with DaaS environments? I didn't realize what it was until 1/2 hr ago. Like Virtual Desktop Environment only it supposedly gives the workstation a new name each time it gets deployed/requested. Did a test upgrade with customer, but didn't move any SI Reports at the time. Today (having gone live last night) asked for the new Tserver like environment so I can install and customer tells me about DaaS. How is SI going to work in this environment? Even if I install on the 'Master', will SI work on the desktops if a different name each time? Ugh! Is this the new technology we now have to deal with? Help!

Nancy, there are many ways to deploy DaaS. Products like Amazon Workspaces, VMware Horizon View, and many others can deliver desktops to the users. The workstations typically don't change names on each access per se, but are usually in what would be a ""Dynamic"" pool of desktop, and the end user could access any of the desktops within that pool. Again, that is only a function of how the pool is configured. Depending on the needs, some organization also set a ""Persistent"" desktop, which is dedicated for the user, and will maintain its name across sessions. I would wager that if the pool is set to Dynamic, you're going to be dealing with more issues than just the name of the workstation changing, but rather the software configuration on each. (again, depending on configuration). To answer your question, this technology has been around for years, more typically deployed within an organization, and is now becoming more available in cloud hosted solutions as well. (i.e: Amazon Workspaces) Hope this helps.

@NancyHanson - I ran into something similar with a Citrix farm - depending on the load, a user could be using one of 4 Citrix machines. We had a 3 user license for SI and ended up purchasing one more license...

We encountered this on Applianz. We set up one workstation that had a fixed, constant id so that SI worked. The other instances are destroyed when user logouts. So to access SI users login to a specific wkstn ID, using the same credentials they do normally. Works fine.

Thanks everyone, customer is realizing today that the non-persistent mode also means user's customizations to Sage get wiped out too. They do a lot of importing so previous path to file will be blank each day, etc. I've dealt with virtual desktops before, just not this non-persistent mode. I certainly understand it more tonight than I did earlier today. We'll see what tomorrow brings and if they can move to a persistent mode for the accounting dept.

For what it's worth, from what I know about Virtual Desktops. Moving from Non-Persistent to Persistent, isn't as simple as flipping a switch. So, expect to be met by a lot of resistance from IT.... just a fair warning :) There are ways to get around through maintaining Sage profiles in non-persistent mode, by using persistent profiles (or Roaming profiles, etc...), but not sure that it'll resolve the SI issue.

George has a point. If you don't have a wingman to argue with their IT, find one. Otherwise you're bringing a knife to a shootout. I suspect that there are a couple 90 Minders who could expand your company's arsenal for this occasion if you need it ...

One could imagine that Sage might have a KB on this issue???