Point all new users at same local profile in Windows 7 (to speed up VDI login times)

Todas las respuestas

• lunes, 30 de abril de 2012 8:23

   

   
  

  0

  Log on to the computer with the user account which you need make the default profile, locate to control panel->Advanced system settings. Click the “Settings” under "User profiles" copy to a location, and then grant full control to everyone. Copy this profile to the Netlogon share and rename the profile to Default User.

  Then please check the status．Thanks.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Responder
  • Citar

   
• lunes, 30 de abril de 2012 15:55

   

   
  

  0

  Hi Joan,

  Thanks for the suggestion, I want to avoid having any profile data be copied down to the local PC, I actually want any new user that logs in to use a local profile that is already established on the PC. The file/folder copy process is what is making the logon take so long.

  Thanks for any suggestion you might have.

  • Responder
  • Citar

   
• martes, 01 de mayo de 2012 8:25

   

   
  

  0

  I would like to let you know that when the user first logon in the domain, system will check the user profilelist, default user folder under netlogon share, default user folder on the local computer, and then copy the information from it.

  In your scenaario, I suggest you can put the default user folder on the local computer, and ensure no default user folder under netlogon share folder. Then the new user will load the profile from local.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Propuesto como respuesta Joan Zhang - MSFT miércoles, 02 de mayo de 2012 9:42
  • Votado como útil Joan Zhang - MSFT martes, 08 de mayo de 2012 8:59
  •  
  • Responder
  • Citar

   
• martes, 01 de mayo de 2012 19:45

   

   
  

  0

  Hi Joan,

  The way you describe it is how we have our system(s) set up now, we do not have a default user profile in the netlogon share and we do have a customized local default user account on the Windows 7 system, the problem is it takes too long for that local default user profile to be copied over to the new user's profile folder at logon. Since VMware destroys any data written to disk (including the new user's profile) upon logout you have to suffer through the profile rebuilding process on every logon. We are trying to map any new user to use an existing local profile already established on the Windows 7 box to save time but it looks like it can't be done. :-(

  Thanks for the suggestions though

  • Responder
  • Citar

   
• viernes, 04 de mayo de 2012 6:57

   

   
  

  0

  Hi,

  I would like to know if you need any assistance on this. If not, please mark it as answered.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Responder
  • Citar

   
• viernes, 04 de mayo de 2012 13:29

   

   
  

  0

  Hi Joan,

  Unfortunately my question has not been answered. What I want to do (have all new users share an existing local profile... not copy a default profile to become their new profile) I believe can not be done.

  • Responder
  • Citar

   
• viernes, 04 de mayo de 2012 14:47

   

   
  

  0

  Hi Brian,

  what Logon Times do you get?

  I have Logon Times (welcome displayed)  from about 10-15 seconds with the default profile created according to the sysprep/copyprofile Method.

  I gets slightly faster if i user local mandatory profiles. But in my testing i was never faster than 7-8 seconds.

  What i found: you can create a mandatory Profile with one user and set this user to use his "own" Profile as mandatory an get Logon Times of 2-4 seconds what can be perceived as "instantly".

  This is even the case if the profile for the user didnt exist before... so what takes the time is NOT the copying of the mandatory or default Profile.

  What takes the time is a change of Name or Sid - user the same profile for a different user it would load 7-8 seconds again even if you replace occurences of the user name with %username%

  What i am testing right now is the use of a mandatory  dummy_user together with Novell Client. I now this is  daring it will possibly break many Applikation because of the wrong %username%.

  Another thing i found that the ActiveSetup Component {89820200-ECBD-11cf-8B85-00AA005B4340} will cost 30 seconds at login time if Folder Redirection is used. (My documents and desktop). Can be reproduced running the stubpath command "start /wait regsvr32.exe /n /i:U shell32.dll".

  Another  game breaker so far is that IE9 typed URLs seem to persist at some place that i havent foud yet: Local Mandatory Profile with Internet Explorer 9 wierdness

  best regards

  MArkus

  • Responder
  • Citar

   
• viernes, 04 de mayo de 2012 18:02

   

   
  

  0

  Hi Markus,

  The place where our virtual desktops hang for the longest time is at the "Preparing your desktop" screen, the "welcome" portion of the screen goes by really quickly. You know what is funny is we were actually able to knock a few seconds of the load time by redirecting the user's My Documents and Desktop folders to a network folder share using group policy. I was able to shave off a few more seconds by allocating a 2nd processor and more memory (from 1.5 GB to 2 GB) to each virtual desktop and by triggering my group policies as local group policies within the master image instead of using domain group policies. We still are not getting great logon times.... its about 53 seconds from the VMware logon until you get to the Windows 7 desktop. One product we are researching right now is Liquidware Labs ProfileUnity, supposedly it will knock down the login times considerably but we haven't finished the test install yet.

  Can you speak a little more to this paragraph you mentioned...?

  -----------------------------------------------------------------------------

  What i found: you can create a mandatory Profile with one user and set this user to use his "own" Profile as mandatory an get Logon Times of 2-4 seconds what can be perceived as "instantly". This is even the case if the profile for the user didnt exist before... so what takes the time is NOT the copying of the mandatory or default Profile. What takes the time is a change of Name or Sid - user the same profile for a different user it would load 7-8 seconds again even if you replace occurences of the user name with %username%

  -----------------------------------------------------------------------------

  Are you using all local accounts? With VMware View the accounts have to be from the domain. What I have been trying to do is somehow point all domain users to an existing local profile but I haven't had any luck. Feel free to contact me off list gibson_brian AT wheatoncollege.edu

  • Responder
  • Citar

   
• viernes, 04 de mayo de 2012 22:17

   

   
  

  0

  Hi Brian,

  53 seconds sound like an active setup problem. look at hklm\software\microsoft\activesetup\installed components. this commands will be run beforere the desktop appears. compare this to the HKCU hive every installed comonetent that is missing will be run. you could preload the components in your default profile. after that your logon will be significantly faster. then run each stubpath command from the command line with start /wait to get a feeling for the time they need. as i mentioned most of them are fast except {89820200-ECBD-11cf-8B85-00AA005B4340} this will cost 30 seconds if folder redirection is enabled. {2C7339CF-2B09-4501-B3F3-F3508C9228ED} = Themes setup. use it, you will get black desktop otherwise. >{60B49E34-C7CC-11D0-8953-00A0C90347FF} IE Branding i omit this one because i dont use IEAK Branding.

  if you see "preparing your desktop" youre not using the MS recommended way of creating a default profile which is described here: http://support.microsoft.com/kb/973289  however this profile will not inherit all the settings you configure with the amdinistrator account and also the username "administrator" will appear. you could eventually replace it with %username%.

  yes i use all local accounts the novell ZCM DLU creates a dynamic local user after sucessful novell login. this means every logon is a logon of a new user for the workstation. disregarding roaming profiles now i have 3 Options:1.  use the default user profile (sysprep-copyprofile-method) which is save and i recommend to start with. 2. local mandatory profile for all users (use LGPO to set mandatory profile path) . option 3: one dummy_user with mandatory profile created from dummy_user itself. somehow that is what we had 14 years ago with novell client and windows 98. only that today a total separation of system and user profile "steady state" is supposed to work. (what in fact still seems not to work) : http://technet.microsoft.com/en-us/library/gg241178(v=ws.10).aspx

  im not sure if the vdi profile products address problems like this. i would not spend money for the redirect of "my documents" and "desktop" this are 2 simple registry entries.

  regards

  Markus

  • Responder
  • Citar

   
• martes, 08 de mayo de 2012 9:09

   

   
  

  0
  If you would like to make the new user copy the default user profile from local, I suggest you can manually make the default user profile on the local machine. At the same time, ensure no default user profile in the netlogon share folder. Then the new user will load the profile from local.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Responder
  • Citar

   
• martes, 08 de mayo de 2012 15:27

   

   
  

  0
  Hi Joan, what you described is how we have it set up now but just the process of having the default local profile being copied over to the new user profile is taking too long. What I want to do is have any new user that logs in have them use an existing local profile.  For example, I would create a new local user named "template" in my master image and configure it the way I want. I would then (somehow) point a user who hasn't logged into the system yet (say the user's name is "bob") to use the "template" profile located in C:\Users\template instead of having the default profile copied to C:\Users\bob. I have tried setting various NTFS permissions on the C:\Users\template folder and putting registry entries into HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIndows NT\CurrentVersion\ProfileLIst to try and map any potential new user login to the C:\Users\template profile but with no luck. :-(
  • Responder
  • Citar

   
• martes, 08 de mayo de 2012 15:48

   

   
  

  1

  Hi Brian,

  you dont need "various NTFS Permissions".

  The task is: Setup Workstations where every Login is a login of a new user by definition.

  Option 1 to do this: default user profile  (google: sysprep copyprofile)

  Option 2 to do this: Mandatory Profile. You can even  set up a Local Mandory Profile (c:\users\mandatory.V2). You can configure Mandatory Profiles for all users as per GPO Machine-Setting under Profiles. You omit the V2 then (c:\users\mandatory)

  If you are familiar with these technics you can try to tune the profiles further. But i belive you can not get faster logon times as 10-12 seconds with 1) and 7-10 seconds with 2)

  Keep in Mind: The folder Structure c:\users\mandatory.V2 needs read acces for everyone.

  And in the registry structure ntuser.dat you need full acess for everyone. This is security Problem only on a Terminal Server.

  If youre trying to tune the mandatory and include the usrclass.dat  you also have to give full access to everyone (use regedit - load usrclass.dat - set permission)

  best regards

  Markus

  • Responder
  • Citar

   
• martes, 08 de mayo de 2012 15:52

   

   
  

  0

  I second disabling all the active setup keys in autoruns for a faster new user login, especially in 64 bit win7 which has twice as many.  It's all about reducing drive seeking.

  
  

  • Editado JS2010 martes, 08 de mayo de 2012 15:53
  •  
  • Responder
  • Citar

   
• martes, 08 de mayo de 2012 15:56

   

   
  

  0

  Hi Markus,

  I will try the mandatory profile suggestion... I tried it a while back but I'm pretty confident I was not doing it right :-) 

  Thanks!

  • Responder
  • Citar

   
• martes, 08 de mayo de 2012 16:00

   

   
  

  0

  in my setup i disable only 2

  {89820200-ECBD-11cf-8B85-00AA005B4340} Windows Desktop Update

  >{60B49E34-C7CC-11D0-8953-00A0C90347FF}  IE Branding

  I dont use IE Branding and the first on makes the loading delay for 30 with folder redirection.

  There could even be  problems  disabling Windows Desktop Update. i read the recent Folder would not display correctly then.

  • Responder
  • Citar

   
• domingo, 13 de mayo de 2012 8:07

   

   
  

  0

  Hi Brian,

  I would like to know if the above suggestion works for you. Please keep me posted on the status on your end.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Responder
  • Citar