VM Pro and Windows XP limitations 6

[Yaze]

I hope this my help some in case you didn't know.

When choosing the OS for VM Pro installation you have to bare in mind this :

- Windows XP Home , 5 concurent connections MAX
- Windows 2000/XP Pro , 10 concurrent connections MAX
- Windows 2000/2003 Server , license related.

By concurrent connections i understand each and every simultaneous connection to the PC, meaning :

- every single call in the call flow or access to a mailbox is a connection
- a CCC user accessing the CCC*
- a network print request is a connection*
- a tftp request is a connection*
- etc...

*If running thoose services on the same PC.

So when choosing your OS make sure you count every possible concurrent connections you could have ( VM ports licenses, CCC, Print Server, Tftp Server, etc...) and make your choice to avoid a limitation problem.



Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[dphoneguy24]

Is there a document from Avaya that explains this?

Thanks,
dphoneguy24

 

[BigNads]

That statement is wrong on many levels.

Wrong.

Wrong.

Wrong.

 

[jml2665]

BigNads, can you please explain

 

[Palecek]

The concurent licenese are for file shares, which is not used by VoiceMail in any way shape or form.

VoiceMail works of IP from IP Office to VoiceMail Pro on it's own protocol... not via "concurrent" connections.

So it has nothing to do with that.

 

[dencom]

in fact, it's possible to 'upgrade' your xp pro client to support many more connections. It's a registry thing but can be done.

Arnoud

 

[Yaze]

http://support.microsoft.com/?scid=kb;en-us;314882

I was told that every access to the VM was a different Inbound connection by Avaya...


Had many troubles with xp machines on populated systems and none with Windows Server...

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[tmgpbx]

I have to disagree with Yaze. With that generic response that would mean an XP Home box with a 4 port VMPro connection and the license file would match the XP Home box conncetions? I have setup XPpro with as little as possible in the client area and have had VMpro, CCC, IMS, wallboards w/o a problem.

What Palecek says is right on, Avaya doesn't use file shares.

 

[BoyRacer1001]

tmgpbx, They do use shares for CCC, primarily the reason they no longer support XP or 2000 as the CCC server.

 

[avayaconsultant]

Keep in mind that for VM Pro, there is only one connection. The IP Office talks directly to the XP machine. The phone connects to the IP Office and the IP Office to XP. That is only one connection. The MS article above referenced other "computers" attaching to the XP Box. There is only one other "computer" attaching and that is IP Office.

 

[Yaze]

Well let's say that any connection from the IPO is considered as one by the XP VM machine ( and i m not sure about this because i was told diferently when i called the techs from avaya ), even then if you have a XP home machine and you have 10 ip phones making a tftp request, at the same time, 5 are not going to go through, same goes for anything trying to connect at that moment being a ccc user accessing the report htlm page, an access to the the VM, or any new connection to the machine...

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[avayaconsultant]

As a recommendation... Don't use XP Home edition for IPO applications. In the future, if you have to network the system on a domain, you are stuck upgrading to XP Pro to have any domain functionality. Maybe XP Pro just has better handling on these issues you are having. Almost all of our systems have been deployed with XP Pro and no issues yet. (Crossed fingers)

 

[Yaze]

XP Pro just doubles the windows server services connections to 10... But it's still caped at 10

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[JayNEC]

that cap can be lifted:

http://www.lvllord.de/?lang=en&url=tools&PHPSESSID=0766cd8b6da3b4b3d23278d82255a615

 

[troyz]

Nice to know! Thanks

 

[Yaze]

That is for half open tcp connections, to cap them at 50... It has nothing to do with the 5 (XP home) 10 (2000 pro, XP Pro) HARDCODED server service connections (file, print server, tftp, etc...) This thread is about

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[phantomiii]

Does anyone here really know what they're talking about in regards to the limitation??? Can anyone verfiy the validity of these statements everyone is making?

 

[Yaze]

The limit this thread was about is the hardcoded cap of 5 and 10 (xp home, and xp pro 2000 pro) have on connections for server services (ie, http, ftp, tftp, files shares, print shares, etc...)... The ambiguity is on how the vm connections are treated by the operating system which i was told by avaya that they were each handled the same way and making each one a connection (I'm going to reverify this with them) but this thread is still applicable as far as CCC, TFTP, etc...

The patch to cap at 50 the 10 limit is for HALF-OPENED TCP connections, that cap only came with SP2 (XP) and has nothing to do with the 5/10 client/server connections limited in 2000/XP.

I'll be back

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[Yaze]

I just hang up the phone with avaya and they've confirmed again. No matter how my question was phrased ie "If you run a 20 ports Voicemail Pro Server on an XP Pro machine only 10 clients will be able to connect at the same time".

Now, if anyone want to tripple check this feel free to do it, too much information never hurted anyone )

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[intrigrant]

It depends how "clients" are interpreted, Microsoft does not mention clients or connections but calls it "devices".

From the Microsoft XP EULA:
• You may permit a maximum of ten (10) computers or other electronic devices (each a “Device”) to connect to the Workstation Computer to utilize the services of the Product solely for File and Print services, Internet Information Services, and remote access (including connection sharing and telephony services). The ten connection maximum includes any indirect connections made through “multiplexing” or other software or hardware which pools or aggregates connections.

Reading this i assume that the IPO is one device connecting to XP, i have seen quite some 10+ port VM Pro's on Win XP running without any problem.

Futher more is's a bit stupid to "tweak" or "hack" a standard licensed operating system to go beyond the maximum licensed connections. It may very well de-stabilize the PC with all troubles it brings you at customers site.