Launch Wildfire off server

[angelina-sherid]

I have my test servers setup for Intralink9.

I want to start training my users but don't want their current wildfire3 to interact with it.

I want to install wildfire 4.0 on an application server and have the users launch it across the network, I have done this before but can't remember how. I shared the wildfire 4 folder on the server and created a shortcut on a client machine but it will not launch. I'm sure I'm missing something simple.

Regards,
Angelina

[ptc-1817592]

Hi Angelina,
Unfortunately, Wildfire 4.0 is not supported on Windows Server platforms, where WF3 used to be. We ran into the same issue here in our classroom environment where we had loaded WF3 on the server and launched from there with no problems. When we installed WF4 on the server and it wouldn't launch, I opened a tech support call. Even though you won't find Windows Server platforms on the WF3 Platform support page, it did work, unofficially. WF4 will 'officially' not work on any server platforms - either 2003 or 2008. The call was #6415443 - not sure if you can access it. There was no real explanation as to why WF3 worked but WF4 won't work from a server. You could hypothetically run it from a server if the server was running XP/XP Pro, but I've heard that XP limits the number of connected users to around 10.
Best Regards,
Matt

[Bill_Kunz]

We were un-aware of the Server limitation for WF4, so we just loaded it
up like we do with WF3 and it works like a charm, no problems at all.

We are running it on a Windows 2003 server SP1 x32, WF4 M040.

[bryan_puch]

WF4 work running from Windows server just as well as WF3. The most common problem I've seen is that the cad users tries to run WF from a drive mapping that is different than the drive WF was original installed on. For example, the install was run from the server and installed on drive C. While the network users has mapped the install point as drive W. To resolve this, map the same drive letter for all ProE users, such as W. Then run ptcsetup.bat W, run through the setup and then when it is done it will correct all the paths in the batch files. Now ProE should run as normal. HTH

Bryan