We are getting ready to move Arev from it's current location on a W2K server to a new W2003 Server. If I remember correctly, we don't need to install Arev but just copy the directory to it's new home, set server only to 0, then install the NT Service and Network performance pack set, server only back to 1, and everything should work.

We'll have to update the batch files that are used to start Arev to point to the new server. I'm hoping we can just remap the users drive to the same letter as the old server/share so we won't have to modify anything on the workstations. All our datalocations are aliased and, we have some export programs to modify and a couple of server tasks to recreate, but that should be it. The printer captures are in the batch files so that should all still be good since the print server is not changing.

We use CPU+, from looking at the documentation it appears that that should come over with the copy.

So; has anyone moved Arev to Windows Server 03 with success or had problems running Arev on Server 03? And if anyone sees anything obvious I'm missing, please don't hesitate to point it out.

Thanks in advance;

David Craig.

ABC-Clio

David,

IF you keep all your mapping/pointers etc the same you should not have any problems. Are you going to use same server name?

We are changing the name of the Server but mapping the Arev's directories to the same drive once we change over. At least that's the plan at this point.

Some details I neglected to put in the initial post;

Arev 3.12, NT Service 1.5, Workstations are W2K with shortcuts that point to batch files which capture printers and calls Arev;

forcedos Arev appname /x /m4096

Servers and workstations are all service packed up.

Thanks for listening;

David Craig.

After doing a more thorough search I see that some people are having significant problems with Server 03; performance degradation with the 1.5 W2K Service and issues with write behind caching.

I will add extra time for thorough testing so we can be sure that we don't have these issues before going live.

David Craig.

David,

My only caution - the 1.5 Service is not officially supported on 2003 Server. It may work - but we have seen too many cases where depending on the configuration, it won't. We support using either the 2.1 Service using TcpIp, or the Universal Driver on Windows 2003 Servers.

Hope it helps,

Kevin

That's extremely relevant, Arev has been virtually trouble free since we moved it to it's current home and I would prefer to keep it that way. I'll see about getting approval to purchase the 2.1 Service.

Once more question: I read Sprez's post about DEP and AELS problems with OI, is this a problem for Arev as well as OI?

Thanks;

David Craig.

From observation it would seem possible but the case is not yet as overwhelming as it is for OI.

The Sprezzatura Group

World leaders in all things RevSoft

Could we get an updated what supports which version matrix over in the Products area? The matrices there seem several years out of date (some don't go past 4.12 OI support or include the UD).

David,

DEP should not be an issue while running the 2.1 Service.

Kevin

Sorry yes should have clarified that!

The Sprezzatura Group

World leaders in all things RevSoft

View this thread on the forum...