Follow

List of GPO security settings which prevent ProfileUnity from functioning properly

Product: ProfileUnity

Product Version: 5.5

Expires on: 365 days from publish date

Updated: May 28, 2013

 

Problem:

This is general guidance to list ProfileUnity security requirements.

Symptoms:

ProfileUnity is not functioning as designed.

Possible Resolution(s)

  • Regedit32.exe users permissions must be read/execute
  • Regsvr32.exe users permissions must be read/execute
  • Regedit must be able to execute silently

Description: It’s possible to prevent users from accessing registry tools but it should not be disabled from running silently.

Example:

Policy0.jpg

Description: If "Access to registy editing tools is restricted" than regedit must be able to run silent for ProfileUnity to execute properly.

Example:

Policy1.jpg

  • File system scripting object must be enabled
  • Execution of VBS scripting must be allowed

Description: VBS should not be blocked, check to make sure that this GPO setting is NOT in place.

Example:

Policy2.jpg

  • HKCU RunOnce must be allowed, must not be disabled in GPO
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Description: Usually "RunOnce" is disabled by this GPO policy found here. Verify that it is set to "Not Configured"

Example:

Policy3.jpg

 

  • If GPO is used to limit size of profile it should be set to 100 MB or more or disabled.

Description: This GPO setting is found here. Verify that it is set to "Not Configured"

Example:

Policy4.jpg

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.