Hi,
We experience disturbers issue with user roaming profile,
After I recompose a pool , always there are few users (randomly) that their profile is not upload to the new desktop, they get a clean default desktop,
and not all the GPO defines is working.
Sometimes it solved by log off an logon again, but always I have a user that I need to configure his profile from the beginning, the outlook software opened like a new application.
Is someone has advice or experience this issues too?
Liora
We've always had (relatively rare) problems where machine policy is not processed at startup. Breakage of roaming is the main issue for us. I'm uncertain if life is any better with persona, as our testing was superficial. As a workaround, we force policy update at boot by repeatedly calling gpupdate until success. Current environment is View 6.2 with 64-bit Windows 7 desktops, refresh on logoff.
Hi,
Thank for your reply,
When you recompose the pool , after make change on the golden image, is the option: reuse the name of computer is set?
How did you do it and where :"we force policy update at boot by repeatedly calling gpupdate until success"
Every time I run recompose I have problem in the morninig with few users.
Liora
Our scenario is linked clones and we do not select "allow use of pre-existing". Possibly we are talking about different issues. My reply is for the case that machine group policy fails to process at startup (as seen in event logs). This failure is not necessarily from a recompose, and occurs often enough that we needed a workaround. If all you care about from machine policy is the setting for roaming profile location, then MS describes other ways to set (user object, local profile) that might be acceptable. We don't control the user object, and we have other machine policies we'd like from AD, so we force policy update at boot by "gpupdate /target:computer" until success. Launch is from sched tasks, and we run only if join-domain has succeeded.
Alrighty, roaming profiles. They are one of the more complicated setups and when you add Horizon View, well you have a lot of moving parts and it only takes one to stop it all.
The bigger problem then the actual behavior of the issue is identifying the potential causes due to the complexity. I'll list out some potential causes and also next steps.
My suspicion would be DNS/DHCP with the hostname not matching the IP which causes a cascade effect.
Also, in reference to setting a pool to "not use pre-existing computername." Bad news on that, it sounds like it would not use previous computer names like VM-01. However, it in fact looks for a pre-existing AD computer object with the same name and only then will it not reuse it, otherwise it will cheerfully reuse computer names.