Active Directory - Wireless Access

Issue: Internal wireless was having trouble authenticating a user.

Resolution:

• Grant user access to Wireless Access group in AD
• In the properties of the "Dial-In" tab, make sure to check "Allow access" under the Remote Access category.

Active Directory, Internal Wireless, Dial-In

Temporary Windows Profile (XP, Vista, 7, 8...)

Symptom: When a user logs in, it gives the warning that "Your profile did not load properly...". This usually indicates that the user was logged in with a Temporary Profile. The following is one method of resolving this:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

To resolve this problem, follow these steps:

1. Log on to the system by using an administrative user account other than the user account that is experiencing the problem.
2. Back up all data in the current user's profile folder if the profile folder still exists, and then delete the profile folder. By default, the profile resides in the following location:
   %SystemDrive%\Users\UserName
3. Click Start, type regedit in the Start Search box, and then press ENTER.
   If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
4. Locate the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
5. Under the ProfileList subkey, delete the subkey that is named SID.bak.
   
   Note SID is a placeholder for the security identifier (SID) of the user account that is experiencing the problem. The SID.bak subkey should contain a ProfileImagePath registry entry that points to the original profile folder of the user account that is experiencing the problem.
6. Exit Registry Editor.
7. Log off the system.
8. Log on to the system again.

After you log on to the system, the profile folder is re-created.

Active Directory - Persistently Locking an Account

A user on our domain had his network password saved in a service that constantly authenticates through the PDC.

The user changed his password.
His account was continually locked, no matter how many times unlocked, it would return to being locked.

This was resolved by removing his credentials from the service described in the beginning of this post.

TIP:
A network password should never be saved into a service that will not automatically update the password credentials upon changing through AD or the Windows password prompt/service.

Google Apps Sync (Manual)

How to manually run Google Apps Sync for our business.

Log in to PDC
Start -> All Programs -> Accessories -> Scheduled Tasks - voila (pick yer poison)

Spiceworks Scans - Again

Issue: Cannot view "Running Processes" of a device under the Devices - All Devices -> Specified Device -> Tools

No technical resolution here.

Simply removed the specified device from the Spiceworks inventory, then set a network scan to scan the devices specific IP.

Once the scan completed, viewing "Running Processes" was available.

- Spiceworks Scans, Spiceworks, Network Scans, Running Processes, Spiceworks Inventory