"Can vWorkspace be proposed and deployed to a Novell eDirectory only environment?"
short answer: no
I did setup vWorkspace 7.6. desktops for Novell Logon.
In my setup the Machines (Hyper-V, vWorksapce broker, Desktops) are all deployed in AD.
The InstantProvisioning Service on the Virtual Desktop needs AD joined Computer Objects. I Recomment InstantProvisioning over Sysprep. For any changes to the Master Template i just boot the Domain Joined Master make changes and do a "slmgr.vbs /rearm" - shutdown - import new template thats all. No sysprep or anything here.
How then provide Novell Logon to Users?
They need to logon to vWorkspace - this can only be done with an AD or local Windows Account (Version 7.6). I use a local Windows Dummy Account on the vWorkspace Broker Machine and prefill the credentials into the WebAccess Web Site.
I will not use the Windows dummy Account for Desktop Access because this could lead to overtaken Sessions in worst case.
To achieve this:
I disable pncredprov.dll on the Desktops
Setup the Desktops to use RDP Security Layer - this will bring up the Interactive Welcome Screen for Logon.
The actual logon is done by a combination of pgina.org and Novell Client. Pgina provides LDAP Authentication and creates a local Windows User on the Desktop. Novell Client in passthrough mode will do Novell Authentication - seemless for the User.
In this use case we do not need user Profiles. Instead i use a "predefined" Profile for the newly created user. I setup the Computers to reprovision after logout - so its a one way thing.
vWorkspace 8 with the "anonymous" Feature could be useful. I think AD is still needed for Machine Accounts and InstantProvisioning.
mwehr
34 Posts
892
0
Posted June 26th, 2013 08:00
Hi Cyrill
"Can vWorkspace be proposed and deployed to a Novell eDirectory only environment?"
short answer: no
I did setup vWorkspace 7.6. desktops for Novell Logon.
In my setup the Machines (Hyper-V, vWorksapce broker, Desktops) are all deployed in AD.
The InstantProvisioning Service on the Virtual Desktop needs AD joined Computer Objects. I Recomment InstantProvisioning over Sysprep. For any changes to the Master Template i just boot the Domain Joined Master make changes and do a "slmgr.vbs /rearm" - shutdown - import new template thats all. No sysprep or anything here.
How then provide Novell Logon to Users?
They need to logon to vWorkspace - this can only be done with an AD or local Windows Account (Version 7.6). I use a local Windows Dummy Account on the vWorkspace Broker Machine and prefill the credentials into the WebAccess Web Site.
I will not use the Windows dummy Account for Desktop Access because this could lead to overtaken Sessions in worst case.
To achieve this:
I disable pncredprov.dll on the Desktops
Setup the Desktops to use RDP Security Layer - this will bring up the Interactive Welcome Screen for Logon.
The actual logon is done by a combination of pgina.org and Novell Client. Pgina provides LDAP Authentication and creates a local Windows User on the Desktop. Novell Client in passthrough mode will do Novell Authentication - seemless for the User.
In this use case we do not need user Profiles. Instead i use a "predefined" Profile for the newly created user. I setup the Computers to reprovision after logout - so its a one way thing.
vWorkspace 8 with the "anonymous" Feature could be useful. I think AD is still needed for Machine Accounts and InstantProvisioning.
best regards
MArkus