HP Neoware e140 Neoware Image Manager 4.6 User Manual - Page 385
Limitations, Data Transfer During Single Client Boot-up, Maximum Clients Attached to a Single Server
View all HP Neoware e140 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 385 highlights
Limitations Troubleshooting CVol spaces will be discarded and your image should then run sysprep automatically. It is recommended that you completely understand what the potential problems of duplicated SIDs could be before you configure Neoware Image Manager clients booting from the same disk image to have different SIDs. Usually, there are absolutely no problems with Neoware Image Manager clients having duplicated SIDs, especially when the clients are member of a domain or when the mounting mode of the system Virtual HD is CVolwrite/Volatile. Refer to the following for more information regarding this matter: http://www.appdeploy.com/articles/sids.shtml http://www.microsoft.com/technet/sysinternals/Security/ NewSid.mspx Data Transfer During Single Client Boot-up Our measurements revealed that a single diskless Neoware Image Manager client that boots Windows XP using the default Neoware Image Manager configuration involves the transfer of approximately 80 MB of data on the LAN. Depending on each configuration, this amount of data may vary, usually between 60 MB and 100 MB. Maximum Clients Attached to a Single Server There is no theoretical limitation to the maximum number of clients that can be attached to a single Neoware Image Manager server. As long as there are enough bandwidth and hard disk resources on the server and network to serve all the client requests in an acceptable time (3 minutes to boot-up in the following example), you can use as many clients on a single server as required. The following considerations are provided to help you design your Neoware Image Manager architecture properly. This section is merely theoretical and stands only as recommendation, nothing here is guaranteed. Limitations 369