Forum Replies Created
-
Posts
-
Through my limited testing I have produced some pretty consistent results. I’ve only tested up to 5 v90’s on Windows 2003 / WDM. Whether imaging a single device or up to 5 devices the times have always been ~30mins for devices on 10Mb Half ports and ~15mins for 100Mb Full ports.
I basically thought the same thing as yourself.. that the disk IO may be the initial bottleneck. The A61 only has a single SATA drive. I think the disk would probably suffer before something, like the NIC, becomes saturated. Currently, at about I’m not sure how caching would behave here and whether the memory subsystem would would be another bottleneck.
Anyways…it’s good to see that your results a more or less consistent with what i’ve seen (i.e ~15 mins to re-image a number of devices concurrently).
thanks for the concurrence pauladam 🙂
It’s starting to look like I’ll probably need to move to Windows server as well since I’m about at wits end in trying to get it to work on XP. I figure if I go to server I will also try to push for WDM Enterprise so we can image more than 5 devices at a time.I actually posed a new question to this forum as to what people’s experience were with the max number of clients they can re-image at one time with a single WDM server. Anyhow, will be interesting to see what type of numbers people have been able to achieve.
Sounds like I’m definitely missing something then. The fact that you were able to image 5 at a time with XP Pro really surprises me…I wonder what is wrong with my setup? I’ve completely re-installed a few times…a fresh install of XP Pro with SP2, applied all MS critical patches and updates, then installed WDM (tried both 4.5.1 and 4.5.2 and WDM Enterprise as well) and nothing else on the box. Left everything more or less at the defaults…and the most I can image at a time is 2 devices. The 3rd device, boots into PXE, gets an IP, and then is always unable to connect to the HTTP/FTP server. It tries numerous times ‘searching for interface’ and getting a bunch of “READ FAILURE” and rebooting before actually giving up. There are no events in the events log that indicate im hitting a stream or connection limit. Is there something i need to tweak or adjust to ensure I can support more than 2 devices connecting?
Appreciate everyone’s feedback…
Confgen – thanks for the tip about WDM Enterprise being required for remote repositories. I skimmed over some of the WDM admin guides to see if using an existing FTP server is a viable approach. So, does this mean that I need to install WDM Enterprise on the XP Pro machine
only? Or does the FTP server also require an installation of WDM Enterprise. It wasn’t clear from what I read in the documentation…sounds like i just need to install WDM Enterprise on the XP guy as the master repository and then have then configure a remote repository to point to an FTP server that it will have read/write access to. Then configure the clients to go against this FTP server to get its updates and hopefully i should be able overcome the 2 connection limit of XP?Thinkthin – thanks for your suggestions about hitting the stream/connection limit of XP. This is what i’ve been thinking all along myself but I can’t seem to find any evidence that this is the case. Like I mentioned, I have already tried the lvllord patch and this is has not made a difference here. Am I missing something here? I’d love to know whether anyone has successfully gotten XP to suport more than 2 concurrent connections??? Otherwise, if this is just impossible without a completely hacked (and unsupported) XP config then I may be just be wasting my time and should push my company to move to a server OS.
Thanks again for everyone’s input 🙂
Hi Pauladam,
Many thanks for your response 🙂
That’s a good suggestion (to use another server as the WDM remote
repository)…never thought of this and will definitely see if this is a possibility.As for the the tcpip.sys patch, I already tried this and it didn’t work. I’ve basically tried all the IIS/reg tweaks and patches I could find on the web to overcome the crippled XP IIS implementation with no luck. I continue to get the same READ FAILURE with the 3rd device that tries to connect to the web/ftp server to get it’s image. This is where most of my frustration stems from…I just don’t understand exactly what is causing this 2 concurrent connection limit (e.g. is it the number of FTP connections? total # of half-open connections? a PXE limitation? etc.). It doesn’t look like XP is hitting its connection limit since I never get an ID 4226 and the fact that the patch did not work.
I guess I would just like to get a definitive answer from Wyse that Windows XP only supports 2 concurrent connections. Their documentation suggests that it can support up to 10 – as per the connection limit for XP Pro (as this is what my company has bought into). However, the responses from other users has suggested that XP only supports 2 connections so there is conflicting info here.
Anyhow….thanks again for your suggestion – it’s most appreciated.
Imstarunit
I’m running WDM 4.5.2 Workgroup on Win XP Pro SP2 and I have the same problem as pauladam. I can’t seem to image more than 2 devices at a time, unfortunately I don’t really have the option of upgrading XP to Windows Server so I’m kind of stuck. Does anyone know of a workaround or way to overcome this concurrent connection limit? I know someone has mentioned that even though XP supports 10 concurrent connections, that WDM uses more than 1 connection to image a device (how many does it use? 5 each device?). However, i don’t see any indication from XP that it’s hitting it’s maximum conncetion limit (e.g. event id 4226 or something like that). All the Wyse documentation that I read says that XP should in theory support 5 concurrent connections. I know that WDM workgroup is limited to 5 connections at a time which is all we need here. TIA 🙂
