File and Storage Services: Verify the Migration

Artigo
08/31/2016

Applies To: Windows Server 2012

Verify that the migration was successful. Follow the appropriate verification steps based on the File and Storage Services role services that have been migrated.

The following overview describes the steps to verify the migration.

Verify the File Services migration

Perform the following tasks to verify the File and Storage Services role migration.

Verify the File Services migration (only if running Windows Server 2008 R2 or Windows Server 2012)
Verify migration of local users and groups
Verify data and shared folder migration
Verify the migration of DFS Namespaces
Verify the configuration on other computers
Verify the File Server Resource Manager migration

Verify migration of BranchCache for Network File Services server key

Perform this step only if the source server is running Windows Server 2008 R2 or Windows Server 2012:

Verify that the server key was migrated correctly by checking the key value, and ensure that the key values are identical on source server and the destination server, as shown in the following example:

Key: HKLM\Software\Microsoft\WindowsNT\CurrentVersion\PeerDist\SecurityManager\Restricted Value: Seed

Verify migration of local users and groups

Check that all the local users and groups you expected to migrate are present on the destination server by comparing the list of users and groups on the Local Users and Groups snap-in on the source server with the list on the destination server.

To open the Local Users and Groups

In Server Manager, click Tools, and then click Computer Management.

Alternatively, you can compare the list of users and groups on the source server and destination server by typing net commands in a Command Prompt window.

To get the list of all local users and save it in a text file, type the following command:
```
net user > localusers.txt
```
To get the list of all local groups and save it in a text file, type the following command:
```
net localgroup > localgroups.txt
```

Verify data and shared folder migration

Check that all the data you expected to migrate are present at the correct location on the destination server and that they have the correct permissions associated with them.

To list files and folders with their permissions, type the following command in a Command Prompt window or in a Windows PowerShell session opened with elevated user rights:
```
icacls <path>
```
Verify that all the expected shared folders have migrated and that they have the correct permissions associated with them. To list all shared folders and their permissions, type the following command in a Windows PowerShell session opened with elevated user rights:
```
gwmi win32_share | %{net share $_.name}
```

Verify the migration of DFS Namespaces

The procedure that you use to verify the migration of DFS Namespaces depends on whether your namespaces are stand-alone or domain-based.

To verify the migration of a stand-alone namespace

Open DFS Management on the destination server.
Right-click Namespaces, or click the Action menu.
Click Add Namespaces to Display.
Type the name of destination server, and then click the Show Namespaces button.
Select the namespace that you migrated, and then click OK.
In the namespaces tree, click the namespace that you migrated.
Click the Namespace tab, and check that all the namespace links are present.
Click the Namespace server tab, and check that the destination server is listed.
Right-click the destination server name, and then click Open in Windows Explorer. All namespace links should be visible in the new window.
Using DFSUtil.exe on the destination server, type the following command for each stand-alone namespace:
```
Dfsutil.exe root \\DestinationServer\Namespace
```
The information displayed should contain the destination server and all the namespace links.

To verify the migration of a domain-based namespace

Open DFS Management, and then right-click Namespaces or click the Action menu.
Click Add Namespaces to Display.
Type the name of the domain where the namespace is located, and then click the Show Namespaces button.

Select the namespace that you migrated, and click OK.
In the namespaces tree, click the namespace that you migrated.
Click the Namespace tab, and check that all the namespace links are present.
Click the Namespace server tab, and check that all the namespace servers are listed.
Right-click the destination server name, and then click Open in Windows Explorer. All namespace links should be visible in the new window.
Using DFSUtil.exe on the destination server, type the following command in a command Prompt window, where \\domain\namespace is the name of the appropriate domain and namespace that you migrated.
```
Dfsutil.exe root <\\Domain\Namespace>
```
The information displayed should contain all namespace servers and namespace links.

Verify the configuration on other computers

To verify that File and Storage Services migration completed successfully on other computers, you must test the configuration on the client computers in your enterprise.

To verify DFS Namespaces on a client computer

Log on to a client computer with the credentials of a user who has access to the migrated namespace.
Verify that you can access the namespace by using File Explorer, a command prompt window, or another application, by entering the same name that you used before the migration.

Verify the File Server Resource Manager migration

Follow these steps to ensure that File Server Resource Manager migrated:

If any custom actions are configured for quota notification or file management tasks, the user should ensure that the folders that contain the executable files configured for the actions and the working folders have the correct access control lists.
As a best practice, ensure that all e-mail message text for notifications, reports, and so on migrated correctly.
Administrators should send a test e-mail message through the File Server Resource Manager console to verify that the Simple Mail Transfer Protocol (SMTP) server is configured correctly for the destination server.
Ensure that expiration folders that are used by File Management Tasks are reachable on the destination server.
Ensure that executable files that are used by custom actions (such as quota notifications and file management tasks) are accessible or executable on the destination server.

Partilhar via