Joining Storefront to Server Group Error “Cannot Join Server Group”

  1. Check for any GPOs that might be blocking any local security policies on server. If this is the case, please block/disable that GPO.
  2. The policy “Access this computer from the network” with location “Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment”, needs to have at least following groups by default:

Everyone

Administrators

Users

Backup Operators

Add COMPUTERS (Storefront Servers)

NOTE: Depending on GPOs applied to environment,

The following table lists the actual and effective default policy values for the most recent supported versions of Windows. Default values are also listed on the policy’s property page.

Server type of GPO Default value
Default domain policy Not defined
Default domain controller policy Everyone, Administrators, Authenticated Users, Enterprise Domain Controllers, Pre-Windows 2000 Compatible Access
Stand-alone server default settings Everyone, Administrators, Users, Backup Operators
Domain controller effective default settings Everyone, Administrators, Authenticated Users, Enterprise Domain Controllers, Pre-Windows 2000 Compatible Access
Member server effective default settings Everyone, Administrators, Users, Backup Operators
Client computer effective default settings Everyone, Administrators, Users, Backup Operators

Related:

  • No Related Posts

Microsoft releases Windows 10 builds 18363.815, 18362.815 with a ton of fixes

Patch Tuesday was only a week ago, but it’s now time for this month’s round of optional updates. Typically, Microsoft does this in several installments, offering updates to different versions at different times. But today, Windows 10 version 1909, 1903, 1809, 1803, and 1607 are all getting updates.

The reason that they’re all getting patched today is likely because this is going to be one of the last times to do it. Starting in May, Microsoft won’t be releasing optional cumulative updates anymore, only Patch Tuesday updates. This is to focus on stability for those working from home during the COVID-19 pandemic.

For those on Windows 10 versions 1909 and 1903, you’ll get KB4550945, bringing the build number to 18363.815 and 18362.815, respectively. You can manually download it here, and these are the highlights:

  • Updates an issue that prevents certain apps from opening after you upgrade from a previous version of Windows, and a Bad Image error message appears.
  • Updates in an issue that turns off notifications for devices that use a virtual private network (VPN) on a cellular network.
  • Updates an issue that prevents you from resuming a Microsoft Xbox game on a Windows device after upgrading from a previous version of Windows.
  • Updates an issue that causes a text box that contains multiple lines of text to stop responding in certain scenarios.
  • Updates an issue that generates unexpected notifications when you change the default application settings.
  • Updates an issue that causes Windows Update to stop responding when you check for updates.
  • Updates an issue that fails to print content that is outside of the margins of a document.

Here’s the full list of fixes:

  • Addresses an issue that prevents certain apps from opening after you upgrade from a previous version of Windows, and a Bad Image exception dialog box appears.
  • Addresses in an issue that turns off notifications for devices that use a virtual private network (VPN) on a cellular network.
  • Addresses an issue that prevents you from resuming a Microsoft Xbox game on a Windows device after upgrading from a previous version of Windows.
  • Addresses an issue that causes a box that contains multiple lines of text to stop responding in certain scenarios.
  • Addresses an issue that prevents the touch keyboard from appearing during sign in when the user is prompted for the password.
  • Addresses an issue that prevents the touch keyboard from opening in Universal Windows Platform (UWP) apps when USB devices are connected.
  • Addresses an issue that displays incorrect folder properties in File Explorer when the path is longer than MAX_PATH.
  • Addresses an issue that prevents the correct lock screen from appearing when all of the following are true:
    • The Group Policy Object (GPO) policy “Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesSecurity OptionsInteractive Logon: Do not require Ctrl+Alt+Del Computer” is disabled.
    • The GPO policy “Computer ConfigurationAdministrative TemplatesSystemLogonTurn off app notifications on the lock screen” is enabled.
    • The registry key HKLMSOFTWAREPoliciesMicrosoftWindowsSystemDisableLogonBackgroundImage is set to 1.
  • Addresses an issue that generates unexpected notifications related to changing the default application settings.
  • Addresses an issue that causes the sign in screen to be blurry.
  • Addresses an issue that causes Windows Update to stop responding when you check for updates.
  • Addresses an issue that prevents the Sign in options page from opening using the ms-settings:signinoptions-launchfingerprintenrollment Uniform Resource Identifier (URI).
  • Addresses an issue with Bluetooth group policy settings on Microsoft Surface Pro X devices.
  • Addresses an issue that causes a KERNEL_SECURITY_CHECK_FAILURE (139) stop error when Windows resumes from Sleep and turns on certain Bluetooth headsets.
  • Addresses a reliability issue in WDF01000.sys.
  • Addresses an issue that causes an error in logman.exe. The error is, “A user account is required in order to commit the current Data collector Set properties.”
  • Addresses an issue that prevents users from setting the REG_EXPAND_SZ keys in some automated scenarios.
  • Addresses an issue that causes a memory leak in the LsaIso.exe process when the server is under a heavy authentication load and Credential Guard is enabled.
  • Addresses an issue that causes the Trusted Platform Module (TPM) initialization to fail with system event error 14 and prevents Windows from accessing the TPM.
  • Addresses an issue that causes communication with the TPM to time out and fail.
  • Addresses an issue that prevents hash signing using the Microsoft Platform Crypto Provider for TPMs from working correctly. This issue might also affect networking software, such as VPN applications.
  • Addresses an issue that prevents applications running in an Azure Active Directory environment from receiving account change notifications. This occurs when using the Web Account Manager (WAM) and the WebAccountMonitor API.
  • Addresses an issue that causes systems to stop working with a 0x3B stop code when running a binary that is signed by a revoked certificate.
  • Addresses an issue with merging Windows Defender Application Control policies that sometimes generates a duplicate rule ID error and causes the Merge-CIPolicy PowerShell command to fail.
  • Addresses an issue that prevents a user’s PIN from being changed after connecting the device to Microsoft Workplace Join.
  • Addresses an issue that fails to print content that is outside of the margins of a document.
  • Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config.
  • Addresses an issue that causes Microsoft Edge to stop working if you attempt to use paste functionality on webpages when cut-and-paste functionality has been disabled using a policy and Windows Defender Application Guard is active.
  • Addresses an issue that causes the Clipboard service to unexpectedly stop working.

Windows 10 version 1809 just had its support extended, and those users will get KB4550969, bringing the build number to 17763.1192. You can manually download it here, and these are the highlights:

  • Updates an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.
  • Updates an issue that causes a text box that contains multiple lines of text to stop responding in certain scenarios.
  • Updates an issue that fails to print content that is outside of the margins of a document.

Here’s the full list of fixes:

  • Addresses an issue that occurs when a third-party application loads hidden tabs into Internet Options.
  • Addresses an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.
  • Addresses an issue that causes a box that contains multiple lines of text to stop responding in certain scenarios.
  • Addresses an issue that prevents the first key stroke from being recognized correctly in the DataGridView cell.
  • Addresses an issue that causes an application that uses msctf.dll to stop working, and the 0xc0000005 (Access violation) exception appears.
  • Addresses an issue that prevents the correct lock screen from appearing when all of the following are true:
    • The Group Policy Object (GPO) policy “Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesSecurity OptionsInteractive Logon: Do not require Ctrl+Alt+Del Computer” is disabled.
    • The GPO policy “Computer ConfigurationAdministrative TemplatesSystemLogonTurn off app notifications on the lock screen” is enabled.
    • The registry key HKLMSOFTWAREPoliciesMicrosoftWindowsSystemDisableLogonBackgroundImage is set to 1.
  • Addresses a reliability issue in WDF01000.sys.
  • Addresses an issue that causes a KERNEL_SECURITY_CHECK_FAILURE (139) stop error when Windows resumes from Sleep and turns on certain Bluetooth headsets.
  • Addresses an issue that causes the Event Viewer Microsoft Management Console (MMC) to stop working when the secondary monitor is above the primary monitor. An out of bounds exception appears.
  • Addresses an issue that causes an error in logman.exe. The error is, “A user account is required in order to commit the current Data collector Set properties.”
  • Addresses an issue that prevents users from setting the REG_EXPAND_SZ keys in some automated scenarios.
  • Addresses an issue that causes a memory leak in the LsaIso.exe process when the server is under a heavy authentication load and Credential Guard is enabled.
  • Addresses an issue that prevents hash signing using the Microsoft Platform Crypto Provider for TPMs from working correctly. This issue might also affect networking software, such as VPN applications.
  • Addresses an issue with merging Windows Defender Application Control policies that sometimes generates a duplicate rule ID error and causes the Merge-CIPolicy PowerShell command to fail.
  • Addresses an issue that prevents a user’s PIN from being changed after connecting the device to Microsoft Workplace Join.
  • Addresses an issue that prevents applications running in an Azure Active Directory environment from receiving account change notifications. This occurs when using the Web Account Manager (WAM) and the WebAccountMonitor API.
  • Addresses an issue that fails to print content that is outside of the margins of a document.
  • Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config.
  • Addresses an issue that causes high CPU usage on Active Directory (AD) domain controllers when migrating to Windows Server 2019. This increases latency in Microsoft Exchange operations, causes Managed Store contention, and severely impacts index creation in Active Directory and the Global Catalog’s performance.
  • Addresses an issue that logs incorrect Internet Protocol (IP) addresses in the audit logs because of missing or old data for active requests coming from “windowstransport/usernamemixed/certificatemixed” endpoints.
  • Addresses an issue that causes devices that are provisioned for Windows Hello for Business (WHfB) to fail. Registration occasionally fails, which leads to a delay in WHfB enrollment and, in some instances, creates Conflicting Objects (CNF) in the Active Directory “Registered Device” container.
  • Addresses an issue that might cause a deadlock in the Remote Desktop Gateway service.
  • Addresses an issue that might cause the Remote Desktop Gateway service to stop working.
  • Addresses an issue that causes systems to stop working with a 0x3B stop code when running a binary that is signed by a revoked certificate.
  • Addresses an issue that prevents the Notification State registries from being deleted for certain apps even after the user profile is deleted.
  • Addresses an issue that causes stop error 0x18 (REFERENCE_BY_POINTER) when Remote Desktop sessions redirect devices that are not input devices.

This one does have one known issue to be aware of:

Symptom Workaround
After installing KB4493509, devices with some Asian language packs installed may receive the error, “0x800f0982 – PSFX_E_MATCHING_ COMPONENT_NOT_FOUND.”
  1. Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10.
  2. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10.

Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows:

  1. Go to the Settings app > Recovery.
  2. Select Get Started under the Reset this PC recovery option.
  3. Select Keep my Files.

Microsoft is working on a resolution and will provide an update in an upcoming release.


For those running Windows 10 version 1803, which is only supported for Enterprise and Education SKUs, you’ll get KB4550944, bringing the build number to 17134.1456. You can manually download it here, and there’s one highlight:

  • Updates an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.

Here’s the full list of fixes:

  • Addresses an issue that occurs when a third-party application loads hidden tabs into Internet Options.
  • Addresses an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.
  • Addresses an issue that prevents the first key stroke from being recognized correctly in the DataGridView cell.
  • Addresses an issue that causes an error in logman.exe. The error is, “A user account is required in order to commit the current Data collector Set properties.”
  • Addresses an issue that prevents users from setting the REG_EXPAND_SZ keys in some automated scenarios.
  • Addresses an issue that causes a memory leak in the LsaIso.exe process when the server is under a heavy authentication load and Credential Guard is enabled.
  • Addresses an issue with running klist.exe that causes lsass.exe to stop working and generates an access violation error (0xC0000005).
  • Addresses an issue with merging Windows Defender Application Control policies that sometimes generates a duplicate rule ID error and causes the Merge-CIPolicy PowerShell command to fail.
  • Addresses an issue that prevents applications running in an Azure Active Directory environment from receiving account change notifications. This occurs when using the Web Account Manager (WAM) and the WebAccountMonitor API.
  • Addresses a Task Manager CPU frequency display issue that locks to the base frequency on devices equipped with certain CPUs.
  • Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config.
  • Addresses an issue that occurs when you try to sign in to Windows during recovery mode. The error, “No administrator accounts are available on this machine”, appears.
  • Addresses an issue that prevents you from removing some local users from local built-in groups. For example, you cannot remove “Guest” from the “Guests” local group.
  • Addresses an issue that prevents certain apps from installing if they are published using a Group Policy Object.
  • Addresses an issue that causes Microsoft Edge to stop working if you attempt to use paste functionality on webpages when cut-and-paste functionality has been disabled using a policy and Windows Defender Application Guard is active.

Finally, Windows 10 version 1607 is still supported for LTSB and Windows Server 2016 customers, and they’ll get KB4550947, bringing the build number to 14393.3659. You can manually download it here, and it has the same one highlight:

  • Updates an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.

Here’s the full list of fixes:

  • Addresses an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.
  • Addresses an issue with Dynamic Data Exchange (DDE) that causes a memory leak when multiple clients connect to the same server.
  • Addresses an issue that causes new child windows to flicker and appear as white squares on server devices that are configured for stark visual contrast.
  • Addresses an issue that causes an error in logman.exe. The error is, “A user account is required in order to commit the current Data collector Set properties.”
  • Addresses an issue that causes a memory leak in the LsaIso.exe process when the server is under a heavy authentication load and Credential Guard is enabled.
  • Addresses an issue that might cause a delay of up to two minutes when signing in or unlocking a session on Hybrid Azure Active Directory-joined machines.
  • Addresses an issue with running klist.exe that causes lsass.exe to stop working and generates an access violation error (0xC0000005).
  • Addresses an issue with merging Windows Defender Application Control policies that sometimes generates a duplicate rule ID error and causes the Merge-CIPolicy PowerShell command to fail.
  • Addresses an issue that might prevent Dynamic Host Configuration Protocol (DHCP) servers from providing the right options to clients when a reservation exists.
  • Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config.
  • Addresses an issue that causes devices that are provisioned for Windows Hello for Business (WHfB) to fail. Registration occasionally fails, which leads to a delay in WHfB enrollment and, in some instances, creates Conflicting Objects (CNF) in the Active Directory “Registered Device” container.
  • Addresses an issue that occurs when you try to sign in to Windows during recovery mode. The error, “No administrator accounts are available on this machine”, appears.
  • Addresses an issue that prevents you from removing some local users from local built-in groups. For example, you cannot remove “Guest” from the “Guests” local group.
  • Addresses an issue that logs incorrect Internet Protocol (IP) addresses in the audit logs because of missing or old data for active requests coming from “windowstransport/usernamemixed/certificatemixed” endpoints.
  • Addresses an issue that might cause a deadlock in the Remote Desktop Gateway service.
  • Addresses an issue in Srv2.sys that might cause 0x18, 0xC2, and 0x19 errors.
  • Addresses an issue that prevents the Notification State registries from being deleted for certain apps even after the user profile is deleted.

This one also has one known issue:

Symptom Workaround
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.

Set the domain default “Minimum Password Length” policy to less than or equal to 14 characters.

Microsoft is working on a resolution and will provide an update in an upcoming release.


As mentioned earlier, these updates are optional. That means that you can get it through Windows Update if you opt into it, or you can install it manually. If you choose to not take the update, these fixes will be bundled into next month’s Patch Tuesday updates.

Related:

User Logon time increased (i.e, group policy processing time of registry and shared printers slow) after 13 Jan standard jdb update

I need a solution

We downloaded Symantec Update 13 Jan 2020 (reduced size for standard clients) and after pushing the update fol issues are being observed.

1. A large no of scripts placed in group policy which are downloaded during user logon are being identified as malware by Symantec. This issue is however solved intermittently by adding the scripts in exception list.

2. The outstanding issue is that now on our Windows Server 2012 R2 application servers, shared printers connect slowly (when you do it via \PRINTSERVERPrinterName) or otherwise when client side extension of printer policy is being executed during user logon. Due to this, user logon times has terribly increased and no log etc is available for troubleshooting. Also, we have even tried stopping sep client using smc -stop command and than try to reproduce the problem, interestingly the problem still is not resolved. However, when we completely removed symantec endpoint client from our server and reproduce the problem, it is gone.

3. After digging down a lot, I also found that not all kinds of printers are being slowly processed during group policy processing at user logon, rather only some HP Laserjet models are slow..

PLEASE HELP!!!

0

Related:

Google Chrome Extension Fails to Install with UPM – 'An error has occurred. Could not move extension directory into profile'

Add C:Users*AppDataLocalGoogleChromeUser DataDefaultExtensionsTemp as a Windows Defender Path Exclusion on the VDA.

This can be accomplished through a Computer Group Policy. The Path Exclusion policy setting can be found in Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Defender > Exclusions > Path Exclusions.

After applying the Path Exclusion, restart the VDA.

To confirm that the Defender Path Exclusion is set, run ‘Get-MpPreference’ in Powershell. The new Defender Path Exclusion should be listed under ExclusionPath.

Related:

Deploy ShareConnect Host Installer

Note: To follow the steps below, you must have a Windows 2012 domain controller. There may be slight differences in the 2008/2003 environments of the domain controller.

1. Log in to the domain controller and open the Active Directory Users and Computers window.

2. On the Active Directory console tree, right-click on your domain to create a newOrganizational Unit (for example, ShareConnect) and add computers you want to install ShareConnect to this organizational unit.

User-added image

3. Open Group Policy Management window to create a new Group Policy Object (for example, Windows SSO) for the Organizational Unit that you’ve created above.

User-added image

4. Right-click on the Group Policy object created and select Edit to modify its properties.

User-added image

5. In the Group Policy Management Editor window, go to Computer configuration >Policies > WindowsSettings > Scripts in the console tree.

User-added image

6. Click on the Properties link under Startup script to open the Startup Properties windows.

Note: You can also right-click on Startup script to open the Startup Properties window.

7. Click on the Add button to open the Add Script window. In the Script Name field enter the script path created here.

Leave the Script Parameters field empty.

User-added image

8. Right-click on the organizational unit created and select Group Policy Update.

This will update the group policy settings of the computers in the domain. If this fails, open the command prompt on your client computer and run ‘gpudate /force’.

User-added image

9. When the user reboots their computer and logs in using their domain credentials, ShareConnect will be installed.

Related:

  • No Related Posts

Deploying ShareFile Drivemapper via Group Policy in a XenApp environment

Drive Mapper Group Policy Example

This guide is a basic example on how to enable Drive Mapper for ShareFile users in Active Directory. This is one example of a possible configuration to only allow Drive Mapper to run for specific users. You must have access to Active Directory Users and Computers and Group Policy Management.

Step 1:

Create a new Security Group. This example creates a Security Group named “ShareFile Users”

User-added image

Add the ShareFile users to the security group. In this case, John Doe is our ShareFile user.

Step 2:

Put all users in an Organizational Unit. This guide assumes all users are in the same OU and will use Group Policy precedence and filtering to disable and enable for the appropriate users. For this example, an OU named “Demo” is created under the domain.

User-added image

Make sure at least two users exist for the example.

This example uses two users, Demo User and Colm. ShareFile Users security group also resides in this OU.

User-added image
Step 3:

Create two new Group Policy Objects in the Group Policy Management Console. This example users “DriveMapperEnabled” and “DriveMapperDisabled”.

User-added image
Link both policies to the OU created in Step 2 named Demo.

User-added image

In DriveMapperDisabled set the policy for Enable Drive Mapper but do not check the box.

In DriveMapperEnabled set the policy for Enable Drive Mapper but make sure you do check the box.

Note: This is the user policy, not computer policy.

Step 4:

Set security filtering on the Group Policy Objects. The desired behavior is for Drive Mapper to be disabled for all users except those which belong to the ShareFile Users security group. The policy security filtering for DriveMapperDisabled should include all users. The default “Authenticated Users” should suffice for this.

User-added image

Click on the DriveMapperEnabled and add the Security Group “ShareFile Users” and then remove “Authenticated Users”.

User-added image

Now each policy has filtering so that all users should have Drive Mapper disabled with the exception of ShareFile Users.

Step 5:

Verify that the Group Policy Inheritance is correct in the Demo OU. Click on the Demo OU in Group Policy Management Console. Click on the Group Policy Inheritance tab.

Make sure DriveMapperEnabled has a higher precedence than DriveMapperDisabled. This will ensure that the enable policy is run after the disabled and allows the appropriate users to use Drive Mapper.

User-added image

Related:

Upgrading from ShareFile Drive Mapper to Citrix Files for Windows

User Settings

Drive Mapper user settings such as Drive Letter is copied into Citrix Files and continue to be enforced.

Group Policy Settings

After upgrading to Citrix Files, Drive Mapper GPO settings will continue to be enforced. If the Citrix Files Group Policy settings are configured, Citrix Files will honor those settings if configured, otherwise it will check if a Drive Mapper GPO setting is configured and enforce it.

User-added image

ShareFile Data Location and Account Sub-directory Mapping

The steps for setting up custom data location and sub-directory paths is slightly different from Drive Mapper to Citrix Files for Windows. In Drive Mapper, there were two GPO settings for custom folder locations:

  • ShareFile Data Location – Local drive or folder path where Drive Mapper stores Folders / Files.
  • Account Sub-directory – Path to the location in ShareFile (such as Shared Folders)

In Citrix Files, the admin can set a custom Mount Point policy as follows:

  • Local Path – specify the local path such as T: or a path c:UsersusernameDocumentsCitrixFiles
  • Citrix Files Path – Path to the location inside ShareFile (such as Shared Folders)

After Upgrade from DriveMapper to Citrix Files, the following conditions could apply:

  1. Citrix File GPO set for Mount Points: Citrix Files mount points will be used and will not check for Drive Mapper GPO policies.
  2. If no GPO is set for Citrix Files or Drive Mapper, Citrix Files will mount the root folder to S: drive (or next available drive letter if S: is already in use)
  3. Only Drive Mapper GPO is set,
    1. ShareFile Data Location and Account Subdirectory GPOs both set: Citrix Files will mount Sub-directory to the Data Location.
    2. Only ShareFile Data Location set: Mount root to the configured Data Location.
    3. Only Account Sub-directory set: Citrix Files will attempt to mount S: to the sub-directory. If S: is not available, Citrix Files does ‘not’ fallback to another drive.

If using Drive Mapper Group Policy definitions, you can recreate similar policy configuration using the Citrix Files Group policy templates. You can learn more about the Group Policy templates from the following article. https://support.citrix.com/article/CTX228273

The following table describes the mapping between the Drive Mapper policy definition and the Citrix Files policy that will need to be configured to match.

Drive Mapper Policy Setting

Citrix Files Policy Setting

User ConfigurationAdministrative TemplatesShareFile

User ConfigurationAdministrative TemplatesCitrix Files

Account

Account

Account Subdirectory

*use Mount Point configuration under Citrix FilesMount Point 1 – 10

Enable Drive Mapper

Enable Application

Excluded File Extensions

Excluded from Upload

ShareFile Data Location

*use Mount Point configuration under Citrix FilesMount Point 1 – 10

Computer ConfigurationAdministrative TemplatesShareFile

Computer ConfigurationAdministrative TemplatesCitrix Files

Cache Location

Cache Location

Cache Size

Cache Size

Delete Cache

Delete Cache on Exit

Enable Auto-Update

Enable Auto-Update

Enable Connectors

Enable On-Premises Connectors

Enable Drive Mapper

Enable Application

Enable Personal Cloud Connectors

Enable Personal Cloud Connectors

Related:

Questions about SEE Administrator, Console and Configuration Manager

I need a solution

Hi, everyone.

I have some question that needs answering:

What permissions do an SEE Admininstrator needs from the AD to work on the SEE Management Console?

Another thing I would like to know if any changes on the Group Policy and AD Computers and Users will be reflected on the Active Directory? If yes, does this means the SEE Administrator will be able to feedle with the AD from the SEE Management Console?

Can we limit the access to the SEE Configuration Manager?

What are the best practises if there’s any?

0

Related: