Hello all,
Just got this query from a client this morning.

>> I wanted to check with you about our Adagio setup with regards to Virtual Vendor’s software. We currently have a virtual machine running that houses the Virtual Vendor Manager software files. The problem is that the Virtual Machine runs on Windows XP, and that is holding us up from switching our Adagio Op locks settings.

All of the other machines on the network are on Win 7, and would be fine to switch over but the Virtual Machine is holding us up.

Here is the part I don’t know about: can we migrate the files housed on the Virtual machine to another workstation (is there really any need to keep them separate on a Virtual Machine?). I don’t know what all is involved or needs to be considered to do this.

We are running into performance issues on many of the workstations, and getting access violations that are interfering with productivity. I am fairly certain that if we get everything onto Win 7, enable op locks and set the server settings, we will eliminate some or many of the issues.

Before I realized the VM issue we did try switching the settings, and things were faster…until we got data corruption messages. <<

Since Peter from Virtual Vendor (VV) set up VV for them, I am not really sure what is required. Can VV be moved to a Windows 7 workstation?

I'd be most grateful for guidance from any of you who have more experience with VV.

Many thanks,
Carol

Without knowing the details about VV's software, perhaps they are running it on a virtual machine, because their OS is Win7 64bit. If they had chosen Win7 32bit, it would likely be equivalent to that XP virtual machine. They'd still need Peter to install VV on a 32bit PC.

Thanks, Bob.

Just an update, she spoke with Peter and they have actually not tested VM Manager (VV) on Windows 7, either 32 or 64 bit. REALLY???? That is insane - how long has Windows 7 been out?

So, for now, they will just put up with what they have - complete with access violations and dismal performance. The VV solution has been frustrating on many levels. I always feel badly when I recommend something to a client and it is so problematic and would love to be able to resolve this for them.

Thanks,
Carol

I don't understand the relationship between the Virtual Vendor machine (which occasionally transfers information up and down from the web) and the rest of Adagio and why you feel the fact that the VV machine needs XP should determine the settings for the rest of Adagio.

Also, has anyone tried running VV on Windows 7? Given the disruption that is implied in your question, would it not be worth just moving VV to an old Windows XP machine in the corner (VV doesn't know and shouldn't care that it's running on a virtual or actual XP platform).

Why not just place the VV software on an XP machine and leave it off in a corner? If necessary, just organize the transfer when others are not in Adagio if it appears that the VV transfers are affecting the other Adagio workstations (if that's possible) or at least during quieter times in the office.

Andrew,
They did email Peter and he sent them back a long email about not having used VV Manager on Windows 7 and it would take about a day to make the change, with the disclaimer that since it had not been used on Win 7 before, there was no telling what the transition might unearth. Their experience has been that changes to fix one thing invariably break something else, so she is hesitant to experiment.

The issue - at least as far as we could see, which could very well be wrong, is that they want to turn OpLocks on. We tried this earlier this year and they got data corruption and a few thousand orphan records in OE. It was not pretty. The only thing that we could figure out to blame this on was the XP machine - perhaps we are wrong?

This is a discussion that I had about this issue earlier this year:
http://www.softrak.com/ubbthreads/ubbthr...31226#Post31226

They followed the instructions in the forum, rebooted all workstations and server and had a myriad of errors.

Any insights would be helpful because the performance currently is pretty dismal and they get enough access violations that they are rebooting 2-3 times per day. This, as you can well imagine, is terribly disruptive to their production.

Thanks as always,
Carol

What Server are they running? There is no mention of a Server in that post. You cannot enable OpLocks in a peer-to-peer environment.

we are running Windows Server 2008

Windows Server 2008 or Windows Server 2008 R2? There's a difference.

Sorry, it is Server 2008 R2 Standard