Since today (18 april 2012) I’m an official Microsoft Certified Solutions Associate (The NEW MCSA)
In the figure below you find my current Microsoft Certifications en Microsoft Cloud-built Certifications.
Since today (18 april 2012) I’m an official Microsoft Certified Solutions Associate (The NEW MCSA)
In the figure below you find my current Microsoft Certifications en Microsoft Cloud-built Certifications.
I will try to explain everything in simple words.
As we know group policy has two main configurations, user and computer. Accordingly, the computer policy is applied to the computer despite of the logged user and the user configuration is applied to the user despite of the computer he is logged on. For example we have a Domain, this Domain has two different organizational units (OU) Green and Red, Green OU contains a Computer account and Red OU contains User account. The Green policy, which has settings “Computer Configuration 2” and “User Configuration 2” is applied to the OU with the computer account. The Red policy, which has settings “Computer Configuration 1” and “User Configuration 1”, is applied to the OU with the User account. If you have a look at the picture below it will become clearer.

If Loopback processing of Group Policy is not enabled and our User logs on to our Computer, the following is true:

As we can see from the picture, the User gets Computer Configuration 2 and User Configuration 1. This is absolutely standard situation, where policies are applied according to the belonging to the OU. User belongs to the Red OU, he gets the Red User configuration 1 accordingly.
Now let’s enable the Loopback processing of Group Policy for the Green OU. In this case if the User logs on to the Computer, the policies applied in the following way:

As we can see, now the User is getting User Configuration 2 despite of the fact that he belongs to the Red OU. So, what has happened in this scenario, the User Configuration 1 was replaced with the User Configuration 2, i.e. with the configuration applied to the Computer account.
As you have probably noticed, the picture above says “Loopback in replace mode”. I have to mention that the Loopback processing of Group Policy has two different modes, Replace and Merge. It is obvious that Replace mode replaces User Configuration with the one applied to the Computer, whereas Merge mode merges two User Configurations.

In Merge mode, if there is a conflict, for example two policies provide different values for the same configuration setting, the Computer’s policy has more privilege. For example in our scenario, in case of the conflict the User Configuration 2 would be enforced.
In the real work environment Loopback processing of Group Policy is usually used on Terminal Servers. For example you have users with enabled folder redirection settings, but you do not want these folder redirection to work when the users log on to the Terminal Server, in this case we enable Loopback processing of Group Policy in the Policy linked to the Terminal Server’s Computer account and do not enable the folder redirection settings. In this case, once the User logged on to the Terminal Server his folder redirection policy will not be applied.
source: http://kudratsapaev.blogspot.com/2009/07/loopback-processing-of-group-policy.html
Project ESX, P4000 ISCSI, W2K8R2, Exchange, Sharepoint, Exact, Datacenter + Disaster Recovery uitwijk locatie etc…. bij één van onze klanten uitgerold, ze zijn marktleider in de Nederlandse Total Facility Management (TFM) @ Com4 Automatisering
Project ESX, P2000 DAS/SAS, W2K8R2, etc…. momenteel aan het uitrollen bij één van onze klanten, “leading importer and distributor of authentic Asian grocery” @ Com4 Automatisering
When I worked the IT department, a fair number of tickets were related to problems with a user’s password. Often it had expired and they were having issues resetting it and needed to logon immediately. If only they hadn’t waited until the last minute! Keeping on top of user passwords is terrific help desk practice. Knowing when a user’s password is going to expire can help you head off a call. Or you may simply need to audit passwords occasionally to identify potential password or security vulnerabilities.
One of the most important password checks you can make is to identify users with non-expiring passwords. I’m assuming this is the exception rather than the rule in your organization. One easy way to identify these accounts is with the Active Directory Users and Computers management console. If you install the Remote Server Administration Tools (RSAT) on your Windows 7 desktop you can accomplish this from your desk and never have to logon to a domain controller.
At the top of the navigation pane you should see an entry for Saved Queries. Right-click and choose New – Query. In the dialogue box enter a name and description. The query defaults to searching the domain root but if you want to limit it to a specific OU, click Browse and navigate to the OU you want to search.
Next, click the Define Query button. This will bring up a dialog box that you can use to create all sorts of queries. On the Users tab under Common Queries you should see a check box for Non-Expiring passwords. That’s what we want. Check it.
Click OK twice and after a moment or two you should get results.
You can manage the users in the results panel like any other user account. By the way, the query you created only works on the current machine. If there are other administrators who need to see this information, they don’t have to re-invent the wheel. Right click on your query and choose Export Query Definition. Save the query to an XML file. The other administrators simply need to Import the saved query on their desktop.
If you have a domain controller that supports the Microsoft Active Directory PowerShell provider, that is to say it must be running the Active Directory Web Services service, you have even more options.
| What Are You Talking About?Microsoft Windows Server 2008 R2 introduced a new approach for managing Active Directory. Any R2 domain controller now runs an Active Directory web service for remote management. Microsoft also released a set of PowerShell cmdlets and a provider for connecting to this service and administering your domain. These cmdlets are also available on Windows 7 when you install the Remote Server Administration Tools and turn on the Active Directory feature. If you do not have an R2 domain controller, you can freely download the Active Directory Management Gateway service from Microsoft and install it on Windows 2003 and later domain controllers. Be aware that installation will require a reboot. But once installed, you can use the PowerShell features from Windows 7 to manage your legacy domains. |
I’ll assume you have RSAT installed on Windows 7. Go to Administrative Tools – Active Directory Administrative Center. This is a new management console for managing via the AD web service. Click the link for your domain or navigate your way to the OU you want to manage. Now we can start filtering.
Because I typically only care about enabled accounts, let’s first make sure we get them. Click Add Criteria and then choose “Users with disabled/enabled accounts”. Also check “Users whose password has expiration date/no expiration date” and click Add. These settings are toggles so you might need to change them. If the disable/enable filter is set to disable, click the link and select enabled. If you want to search the entire domain then use the Global Search link. The settings are the same. After you have made your choices, click Search.
You can manage individual accounts by double clicking them or using the Task pane. I recommend clicking the diskette icon and saving the query for the next time you open the management console. Unfortunately, I have not found a good way to share queries or filters among administrators. The best solution I have found is to click the Convert to LDAP, copy the query and paste it into a text file. Other administrators can paste the query into to a new session and then save their copy locally.
Another query you might find helpful is enabled accounts with expired passwords. Click Clear to start over and add the filtering criteria
The last query that I find especially helpful is identifying users whose password will expire in the next X number of days. Imagine coming in to work on Monday morning and getting a list of users with passwords set to expire the upcoming week. You could take pro-active measures to ensure a smooth update which should make everybody happy.
Clear any search criteria. Add criteria for disabled/enabled accounts and “User with a password expiring in a given number of days.” Verify you are searching for enabled accounts and enter in a value for the number of days. I’ll say it is Monday so I’ll enter 5. Within moments I can see who I need to work with this week.
Unfortunately, there is no way to print, export or otherwise save this information. However, the Administrative Center is actually sitting on top of PowerShell so can bypass the GUI and retrieve information directly from a PowerShell session.
When I worked the IT department, a fair number of tickets were related to problems with a user’s password. Often it had expired and they were having issues resetting it and needed to logon immediately. If only they hadn’t waited until the last minute! Keeping on top of user passwords is terrific help desk practice. Knowing when a user’s password is going to expire can help you head off a call. Or you may simply need to audit passwords occasionally to identify potential password or security vulnerabilitie
Somethimes you want to know when a users is last logon to the domain. Maybe because you want to delete user account which are not logged in for more than a year? Or because a user account is maybe hacked…..
I attached a zip file, with a vbs script and a command file to run this script.
This best practices guide focuses on the following topics:
Citrix XenApp Architecture on vSphere – Provides background on Citrix XenApp architecture and the rationale for deploying on VMware vSphere.
VMware ESX™Host Best Practices for Citrix XenApp –Provides proven VMware best practices for vSphere hosts running XenApp workloads. Includes guidance in the areas of CPU, memory, storage, and networking.
Citrix XenApp on vSphere Best Practices – Deploying Citrix XenApp on vSphere requires that proven best practices for the XenApp application continue to be followed. The focus in this section is on configuring virtual machines for XenApp.
Monitoring Performance – When migrating XenApp to a vSphere infrastructure, maintaining performance levels that are equal or better than those achieved in physical deployments is essential. Monitoring before and after a migration helps validate whether the migration was a success, and can also help establish a baseline understanding of the performance characteristics. This section takes a look at the vSphere tools available to help monitor the vSphere environment.
vSphere Enhancements for Deployment and Operations – Provides a brief look at vSphere features and add-ons that can enhance the deployment and management of XenApp.
Download here: VMWare Citrix Xenapp best practices English 2011 by VMware
GPO Basics or How to live happily with GPOs
GPOs – Group Policy Objects – are very useful for managing domain computers and users, but there are a few not necessarily obvious things to know to get started using them.
You can use the gpupdate command to get changes to Group Policies applied immediately (use the command gpupdate /? to see the options available). With the command gpresult you can see which Group Policies are active to your account/machine (use the command gpresult /? to see the options available).
This is a fundamental, but not necessarily obvious, concept with Group Policies. For this reason, to keep my life simple, I have established for myself, these simple rules:
Like all simple rules, there are some situations where setting them aside makes sense, but there must be a good, rational reason for doing so. One such reason is when “loopback processing” is used.
Thank to Bruce Sanderson’s for sharing this information