Windows 7 cannot access shared folders

Windows 7 cannot access shared folders with error can't find user name.

How to Manage Stored User Names and Passwords

NOTE If you use an administrative account to log on the computer, follow these steps:

1. Click Start, and then click Control Panel.
2. In Control Panel, click User Accounts under Pick a category to open the User Accounts dialog box appears.
3. On the Users tab, click the user that you want, and then click the Advanced tab.
4. Click the Manage Passwords button to open the Stored User Names and Passwords dialog box. A list of stored user names and passwords similar to the following may appear:
   *.Microsoft.com
   Passport.Net\*(Passport)

If you use a restricted user account to log on the computer, follow these steps:

1. Click Start, click Run, type Control Userpasswords2, and then press ENTER.
   
   Note The following message may occur:
   You must be a member of the Administrators group on this computer to open User Accounts. You are logged on asuser name, and this account is not a member of the Administrators group.
   In this condition, you are required to type the user name and password when the system prompts the dialog box to type the user name and password of the administrator of the computer.
2. Click the Advanced tab, and then click Manage Passwords.

To Add an Entry

1. In the Stored User Names and Passwords dialog box, click Add to open the Logon Information Properties dialog box.
2. In the Server box, type the name of the server or share that you want. You can use an asterisk as a "wildcard" character. The following example entries are valid server names:
   *.Microsoft.com
   \\Server\Share
3. In the User name box, type the name of the user account that has permission to access the resource. Type the user name in the Server\User or User@domain.com name format. The following are examples of valid user name entries:
   Microsoft\User
   User@microsoft.com
4. In the Password box, type the password for the user that you entered in step 3, and then click OK.
5. In the Stored User Names and Passwords dialog box, click Close.

To Remove an Entry

1. In the Stored User Names and Passwords dialog box, click the credential that you want, and then click Remove. The following message is displayed:
   The selected logon information will be deleted.
2. Click OK.
3. In the Stored User Names and Passwords dialog box, click Close.

To Edit an Entry

1. In the Stored User Names and Passwords dialog box, click the credential that you want, and then click Properties. TheLogon Information Properties dialog box is displayed.
2. Change the items that you want, and then click OK.
   
   If you want to change the domain password for the user account that is specified in the User name box, click Change. Type the old password and new password into the corresponding boxes, type the new password into the Confirm new password box, and then click OK. The domain password is changed.
3. In the Stored User Names and Passwords dialog box, click Close.

C

Netlogon error after domain rename complete correctly "NlUpdateDnsRootAlias: Updating DnsDomainNameAlias from (null) to old.domain"

Netlogon error after domain rename complete correctly "NlUpdateDnsRootAlias: Updating DnsDomainNameAlias from (null) to old.domain"

Check that AD "msDS-DnsRootAlias" still no contains old domain name and try the following steps to delete the value.

1. Open ADSIEdit.msc. Navigate to the following location.

CN=<domain name>, CN=Partitions, CN=Configuration, DC=<domain name>,DC=local 

2. Right-click on the object and select properties.

3. Verify the attribute "msDS-DnsRootAlias". If any value does exists,
clear the value. i.e. msDS-DnsRootAlias: <not set>

4. Force replication to all the domain controllers.

5. Rename the netlogon.dns and netlogon.dnb file in
%systemroot%\system32\config directory on the problematic domain controller.

6. Stop and restart the netlogon service.

7. Run netdiag to test this issue again.

EXCHANGE Use the Shell to mail-enable a security group

Enable-DistributionGroup -Identity "Server Lab 222"

Disable-DistributionGroup -Identity "Employee Garage Sales"

EXCHANGE Assign "Send on behalf" permission to a distributiongroup (Exchange 2007)

You can grant "Send on Behalf" permissions using the powershell as follows:

Set-DistributionGroup -Identity GroupName -GrantSendOnBehalfTo User1,User2

ANR1534I: Process process ID skipped Num Files deduplicated files on volume Volume name because copies of the files were not found.

Explanation

The DEDUPREQUIRESBACKUP server option is set to YES. If the value of this option is YES (the default), files within a deduplicated storage pool must be backed up to a non-deduplicated copy storage pool before the files can be moved.

System action

The operation skips the files without copies and continues the operation.

User response

Ensure that all files in the primary storage pool are backed up to a non-deduplicated copy storage pool. You can also change the value of the DEDUPREQUIRESBACKUP server option to NO. However, doing so can result in unrecoverable data loss if a data-integrity error occurs. As a best practice, do not change the default.

Cannot install TSM 6.x instance after server rename.

The server was renamed after the TSM server installed. so when trying to installing the instance with the new name it failed.

Solution:


You actually don't have to rename back the server.
Try the following:

db2extsec /r /a DB2ADMNS /u DB2USERS

Remove a server instance without uninstalling the TSM server 6.x

1) Open a DOS command prompt and run “db2ilist”. This will list the TSM instances that are defined to DB2.

2) From the DOS command prompt issue “db2idrop <instance name>”. So if the instance you want to remove is “SERVER1? you would issue “db2idrop server1?

3) Open the registry to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server. Here you will find the instance. Remove the instance directory. Do not remove HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server itself.

NOTE: Before making any registry changes it is always advised to export the registry incase you need to recover.

4) While in the registry the TSM instance service needs to be removed as well. It is located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

NOTE: Before making any registry changes it is always advised to export the registry incase you need to recover.

5) Delete all files located in the instance directory. By default, they are located in C:\Program Files\Tivoli\TSM\<instance name>

6) Delete all log and DB volumes for the instance. The location of these volumes was determined at the time of configuration. There is no default location.

NOTE: Ensure that you are deleting the correct volumes for the instance. If you delete volumes for a different instance than you are removing, that instance will no longer be operational.

7) Also ensure that c:\<instance name> is deleted.

You are now ready to run the config again.