wepct: I think we may be able to help you. We see lots of customers struggling with how to handle "shared PCs".
1. If your helpdesk doens't know what to do, write them a procedure that entails these steps
- Perform a one time boot to get the user into Windows (this requires a challenge response). Also, if you reduce your recovery key size to 64, your helpdesk will be able to do this faster.
- In v6 the code will auto-add the user. In v5, the helpdesk agent will have to go into the console an manually assign them. If you want to take out the manual step here, you can use our command line to simply "setuser" A to machine X. Using the command line can drasticallly reduce your helpdesk call time. If your helpdesk can't handle that, then consider making a web page for them. I think we have the "assign user to machine" as a feature request for our own web helpdesk.
2. If your offices are small enough, you may simply be able to assign every user to every machine. We typically recommend assigning no more than ~250 users to a single machine, but you can expand the size of the SBFS to accomodate more (lots more). The only catch then is that you'd want to reduce your sync frequency because each sync is going to take longer and you don't want to kill the server with concurrent connections. This will take some planning and perhaps some new install sets, but that work could really reduce the burden your helpdesk.
Sorry for deviating from post topic here. wept, feel free to email me email@example.comMessage was edited by: DLarson on 11/6/09 7:08 AM
wepct: I just read the KB. I think you are right. Some (you could argue most) users expect the "last change on the endpoint" to take over, not the "last sync to the server". Let's hope the FRM was processed for v6 or gets processed soon.Message was edited by: DLarson on 11/6/09 7:08 AM