- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm setting up a View 4 deployment in a computer lab. We're using non-persistent linked clones and the client machines are older Dell desktops with View Client installed. I'm trying to set it up so that the machines boot up, connect to their View desktops and STAY in their View desktops. I have the first two parts mostly figured out but that last part is snagging me.
The View desktops are all generic logins that will be scripted for the client machines (users do not have accounts to manually log in).
Any ideas on how to keep them in the session or, if that isn't possible to relaunch the view client?
Finally, does any of this make any sense or should I not be trying to do this? Has anyone done anything similar (public computer lab connecting to View desktop pool with no manual logins)?
Thanks,
Jamie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This should work,
Have you tried a batch file that scripts the View Client logon? You can get the parameters from the View 4 Admin Guide:
www.vmware.com/pdf/view40_admin_guide.pdf
Page 115
Just drop the batch file in the startup group of each Client PC and configure them to log in automatically when they start up, then the windows startup folder launches the batch file which calls the view client and the generic user parameters. You're then in your View Desktop.
This sounds more like a kiosk mode of operation but with students it's nearly the same thing.
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Mike, that's basically what I've got set up so far, but does anyone have any ideas on KEEPING them connected? Either preventing users from disconnecting or making it reconnect if it ever disconnects?
I guess this might be more of a Windows question but I thought I'd see if anyone else was doing something similar. And yes, this would be very much like a kiosk environment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a great document to use. Start on Page 2 for the Windows side. Basically you change the shell of the HKCU to a VBS file that calls the View Client. I use this in my environment. Keep in mind, only do the registry hack for the USER, not the MACHINE unless you have a boot up registry editor.
If you are really brave, take on the Linux make your own project.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. That's exactly what I was looking for.