

DMM Deployment Setup Guide › Working With the DMM Deployment Setup Wizard › Manually Create a Null-Session Share
Manually Create a Null-Session Share
The directory where the DNA files are stored must be a null-session share since CA DMM runs as the System user account. You must set up the null-session share before running any procedures.
To manually create a null-session share
- Start the Registry Editor by running the regedit.exe file.
- Locate the following registry key:
HKEY_LOCAL_MACHINES\System\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionShares
Note: NullSessionShares is a REG_MULTI_SZ value.
- Enter the name of the share you want to access with a null-session on a new line in the NullSessionShares key. For example, enter DNAData$
- Locate and click the following registry key:
HKEY_LOCAL_MACHINES\SYSTEM\CurrentControlSet\Control\LSA
- Click New on the Edit menu, select DWORD value, and add the following registry value:
Value Name: RestrictAnonymous
Data Type: REG_DWORD
Value: 0
- Close the Registry Editor window and restart the server.
- Set the following properties for the shared folder:
- Add 'Everyone' under Share Permissions.
- Add 'Everyone' under the Security tab with full permissions.
- Enable the 'Network access: Let Everyone permissions apply to anonymous users' setting in the Windows Local Security Settings.
DMM Deployment Fails when DMM Source Share is not Linked to an Active Directory
Symptom:
When a DSM domain manager and the agent computer are on Active Directory and the DMM Source share computer is not linked to any Active Directory, deploying the store and applying the procedure on the DSM agent computer fails.
Solution:
The deployment fails because CA ITCM cannot communicate with the DMM Source share.
Follow these steps:
- Enable Guest User Login on the computer where the DMM Source share is available.
- Allow access for Guest User through the network using the following Windows settings:
- Enter secpol.msc in the Run prompt.
The Local Security Settings dialog appears.
- Navigate to Security Settings, Local Policies, User Rights assignment.
- Verify that the guest user is not listed under the deny access to this computer from the network policy.
Guest login is enabled on the computer.
DMM Apply Procedure Execution Fails during the Restoration Phase on Windows Server 2008
When the DMM network share runs on Windows Server 2008 or higher, the DMM Apply procedure execution fails with a runtime error on some of the target machines during the restoration phase.
Follow one of these steps:
- Use a DMM network share that runs on Windows Server 2003 SP2.
- Use a DMM network share that runs on Windows Server 2008 SP2 or Windows Server 2008 R2, with SMB 2.0 disabled as follows:
- Open Regedit.
- Navigate to HKLM, System, CurrentControlSet, Services, LanmanServer, Parameters.
- Add a DWORD key with the name smb2 and set the value to 0.
- Restart the server.
Copyright © 2014 CA.
All rights reserved.
 
|
|