I've moved my blog to http://blogs.msmvps.com/ad please update your records.
While setting up some performance reports in Ops Mgr 2007 I’ve been getting an rsAccessDenied message when I try to dig down into the report.
I setup and scheduled several performance reports to run every day and save them as a Web Archive. I did so using an Admin account through the Ops Mgr console. I’m able to view the report that is generated but when I click on it to get further details I get the following error:
The permissions granted to user 'DOMAIN\username' are insufficient for performing this operation. (rsAccessDenied) Get Online Help
If I run this as the admin user that created it I am able to view it. I tried searching online to find the answer (thus the reason for this post) and there are thousands are possible solutions but none worked for me. It seems I’ve found out the issue and wanted to share with you…and me when I forget in the future
From the SQL Reporting server I opened the following page with an admin account – http://localhost/reports
I clicked Home in the top right corner
Select the second tab Properties
Click New Role Assignment
Add the user you want to have access to browse the report
Check the Role you want (I selected Browser)
That was it for me. Now that user had access to browse the report.
Here is a few one-liner commands to help get info on your Active Directory environment. I don’t think there is any mind blowing commands here but they’ve helped me out. There are literally hundreds of these around the web as well as PowerShell ones but these are the ones that I’ve been using lately.
How to view the Domains you trust and see what those Domain SIDs are:
nltest /domain_trusts /v
A quick listing of your AD Sites:
dsquery * "CN=Sites,CN=Configuration,DC=forestRootDomain" -attr cn description location -filter (objectClass=site)
A quick listing of your AD sites and their Site Links and Costs (sure would be nice if you could spit this out to Visio or something):
dsquery * "CN=Sites,CN=Configuration,DC=forestRootDomain" -attr cn costdescription replInterval siteList -filter (objectClass=siteLink)
Compare time against your forest root PDCe:
w32tm /monitor /computers:ForestRootPDC
Find out which DC for a site is the ISTG:
dsquery * "CN=NTDS Site Settings,CN=siteName,CN=Sites,CN=Configuration,DC=forestRootDomain" -attr interSiteTopologyGenerator
Time and time again I run into an issue that presents me with a SID which I need to resolve. I’ve used a number of tools and scripts over the years to address this issue. I think I have the best and easiest method for me to solve this issue that always seems to pop up.
If you’re new to PowerShell you will want to make sure you have it installed if you want to use this script…and yes it is a script not a command. I do this by opening a text file and renaming it from a .txt file to a .ps1 file. When you try to open a .ps1 file it may open in your text editor but for this you will want to Right Click it and select Edit which will open up whatever you have as your PowerShell editor. Copy the following code into the Script Pane:
$objSID = New-Object System.Security.Principal.SecurityIdentifier `
$objUser = $objSID.Translate( [System.Security.Principal.NTAccount])
Now just save this file and you can run it to return the results of the SID that you place in there. The one thing that will change is the actual SID. In this example i’m using S-1-5-21-768745588-123456789-987654321-500 which is the Well Known SID for the domain Administrator. My results should show me the friendly name. Anytime you change the SID you will have to resave the file but then just Run the script and it will show you the results.
I’m sure there is a way I could make this into an application but I'll leave that fun for those looking to take this to the next step.
I was thinking about writing a post about Active Directory replication but thankfully soon realized that by doing so I could be severely depriving my kids and wife of a happy life. Its not that Active Directory replication is bad or harmful, its just that there is so much about it. I don’t care who you are you probably don’t know it all…I certainly don’t and have never claimed too.
While I was doing my research for this post I found what I'd like to call the bible to Active Directory replication. I’m also thankful this was one of the first resources I picked up on and didn’t have to much time invested. Without further ado - How the Active Directory Replication Model Works. I think if you printed this out it would be about 100 pages or so (not confirmed but it is long).
This article goes over every little detail needed to fully understand the Active Directory replication model. I’d love to know the person/team that wrote this and give them my gratitude. I wish stuff like existed for new products. I still remember trying to learn Active Directory when it was in beta back in 1999 and not fully understanding USNs, Up-to-Dateness Vectors and Watermarks.
If you have any good resources on Active Directory replication please feel free to share so others can learn as well.
I’ve blogged several times about the AD Recycle Bin (ADRB). It has been a popular subject here at the Life of Brian and I can see why. It is a feature all AD admins have been screaming about for years. I wanted to spend 5 mins of your life going over two attributes that confuse everyone…even me from time to time.
There are over a dozen attributes that deal with ADRB but I want to focus on two of them, isDeleted and isRecycled. The first time I read through the documentation on these attributes I thought it was pretty straight forward, isDeleted is when an object is deleted and isRecycled is when an attribute is recycled. Well it is NOT that simple. Let me explain these attributes a bit further for your understanding.
The isDeleted attribute has been around since Windows 2000 and exists on every AD object. It describes if an object is deleted (makes sense) but also if it is restorable. After the ADRB is enabled you have the ability to restore deleted objects (that were deleted after it was enabled).
The isRecycled attribute is new to Windows Server 2008 R2 and only exists on an object after it has been recycled. By default, a deleted object will become a recycled object after the msDS-deltedObjectLifetime (another new attribute in Server 2008 R2) expires. Now that object is what I like to call dead dead. This means that you can’t restore it with all its pretty properties. Its kind of like the old way of restoring an object just to get its SID back.
I think you can see where the confusion comes into play. When I hear or read the term isDeleted my gut reaction is to think that it is deleted (dead dead) and when it says isRecycled I think it can be restored fully…well the sad truth is that it is the opposite.
I do a lot meetings and training via Live Meeting. One thing that has irked me for sometime has been that when I share my desktop it goes into a Basic display mode and disables all the cool Aero features.
I’ve figured out a workaround to this. After you share your screen go the start menu and paste the following into the search box - Find and fix problems with transparency and other visual effects. If you have UAC on it will prompt you to click Yes. The next screen that pops up is a troubleshooter wizard shown below.
If you click next it will go through a process where it checks features and HW to see if Aero can run. If it worked prior to sharing in Live Meeting it should now work after you run it.
I haven’t found a method to save this theme or settings but each time I need it I run this tool and it gives me the ability to run Aero features!
You may be familiar with the traditional ways to transfer FSMO roles but how about by using PowerShell? By now you should just know that PowerShell can do everything the GUI can do…well at least that is the way it feels to me.
If you want to use PowerShell to transfer any of your five FSMO roles (PDC Emulater, RID Master, Infrastructure Master, Domain Naming Master and Schema Master) then you will first need to import the Active Directory Module into PowerShell.
Now that you have the AD module loaded the cmdlet you will use for this is quite large - Move-ADDirectoryServerOperationMasterRole. Thankfully we have the Get-help cmdlet to help us remember that. All I need to do is remember move-ad and then I press tab to complete the rest. There is only one other cmdlet that is similar to it and you just have to remember you are trying to move the FSMO role and not the sever.
When entering the cmdlet you need to specify the operation master roles to move. the syntax for the five roles are as follows - PDCEmulator, RIDMaster, InfrastructureMaster, SchemaMaster, or DomainNamingMaster. To specify more than one role just separate each role with a comma.
An example of me moving the RID Master and PDC Emulater to DC2 is as follows:
Move-ADDirectoryServerOperationMasterRole -Identity "DC2" -OperationMasterRole RIDMaster,PDCEmulator
A feature that I just love in PowerShell is the –WhatIf parameter. By adding this to your code it will do a dry run and let you know what is going to change if you did the command without that parameter.
One key thing to note here is that I am NOT seizing the FSMO role. For that you will need to use NTDSUtil as defined here.
I grew up on the Atari 2600 and because of that it has a found place in my childhood memories. I’ve played my fair share of Halo over the years too. Well what if Bungie was around 30+ years ago and released their mega hit Halo on the 2600? Dream no more…
How cool is this? You can actually play the game too. It reminds me a lot of the game called Adventure for the Atari 2600. Enjoy!
Stale user accounts can be a big problem…even more so when they are not disabled. I’m a firm believer that if you have an account that is not being used it should be disabled. However depending on the size of your Active Directory that can be a daunting challenge. Below you will find a snippet of code that will identify where user accounts are not being used for 10 weeks and then it has the ability to disable them.
dsquery user -inactive 10 -limit 0
The 10 value is for the number of weeks an account has been inactive. If you think you are going to have a lot of these then you may want to change your limit from 0 to something like 50 or so.
Now if you would like to disable them as well you simply add on another portion of code. For safety reasons I prefer to run the code above first to see who is inactive and then once I’ve validated those accounts can be inactive I run the following code to disable them.
dsquery user -inactive 10 -limit 0 | dsmod user -disabled yes
Obviously the account needs to have the appropriate permissions for dsmod to work so watch out for that. Good luck and happy hunting!
Wow, that is a lot of delegating…seriously how many times can you say it in one sentence. Today’s post is one that threw me for a loop. As a domain admin I have the right to configure constrained Kerberos delegation. There may come a time when you want to delegate that out to a user or group.
My first thought was to assign the user/group Full Control on the OU that included the accounts. At this point I would run the following command
setspn -a http/workstation01 adminprep\brian
Surely Full Control would grant me the permission to do this…Failed!!! Insufficient access rights. It is not a “permission” that is needed, it is a “User Right”. So where do you go to assign rights to work with constrained delegation and what User Right is it? Well, you won’t find it in the Local Security Policy.
The User Right that you need to grant is SeEnableDelegationPrivilege. Now where and how do I grant this User Right. Well it turns out you still should delegate Full Control to the user/group that you want to grant this User Right too. Then on a DC you must run the following command:
ntrights -u adminprep\brian +r SeEnableDelegationPrivilege
Just make sure to modify that domain/user to match your environment. Now when I run the Setspn command it works because that account has the correct User Right. You may have to wait for replication to occur if you are in a distributed environment.
Here are two ways for you to use PowerShell to raise your Forest Functional level to Server 2008 R2:
- get-adforest | set-adforestmode -forestmode windows2008R2Forest –confirm:$false
- set-adforestmode –identity netbiosname windows2008R2Forest –confirm:$false
Either way will work. Enjoy
Tip of the day today is to view your Active Directory Tombstone period while using PowerShell
- From a PowerShell prompt, type
- (get-adobject "cn=Directory Service,cn=Windows NT,cn=Services,cn=Configuration,dc=AdminPrep,DC=Local" -properties "tombstonelifetime").tombstonelifetime
The result shows up in days…very cool.
Just make sure to change dc=AdminPrep,DC=Local to match your domain.
SPNs seem to get more and more use these days so I thought it be nice to give an explanation of what SPNs are.
SPNs are used for mapping a service to a user account. You will find SPNs used predominantly with Delegation and Impersonation and a lot of times this is between a web server and another server hosting a service that requires Kerberos authentication. The key here is that Kerberos authentication is required and thus this is primarily used within an organization or a trusted company. An example of this would be when an end user logs on to a web server which then logs on to a SQL server. The web server is trying to authenticate against the SQL server using the web users credentials but it doesn’t have the right to do that type of delegation. If that were the case I don’t think online banking would be…well online. :) Now this is only the case when the web and SQL instances are on separate servers. If they were on the same server you would not need to worry about SPNs.
Kerberos is the key here. Kerberos authentication happens all the time and is very common. The special part of Kerberos authentication is that it requires a ticket that ensures each party is who they say they are. This ensures that a hacker can’t impersonate another user. The only type of delegation that Windows allows is a Kerberos connection. In short the user knows how to contact and authenticate with the web server but has no idea who the SQL server is but needs data from it and needs to authenticate…thus delegation and impersonation needs to occur.
An SPN is a name that Kerberos clients use to identify a service for computer that is also using Kerberos. In fact you can have multiple instances of a service running on a system and each could have its own SPN. SPNs have a specific format that they use which looks similar to this – <service class>/<host>:<port>/<service name> The only parts that are required are the serviceclass and host. For example, HTTP/www.adminprep.com would be an SPN registration for any page on that webpage. You would use the port option if you wanted to specify a port with the service, like this – MSSQLSvc/sqlservername.adminprep.com:3411. More info on the formatting of SPNs can be found here.
SPN names can use short NetBIOS names or long FQDN names. I recommend always using FQDNs as you can have potential name conflicts in a multi-domain forest with short names.
For a more detailed looked into SPNs i’ve provided a few links below along with links to common issues. However the first place you should go is to this TechNet article.
Service Principle Name (SPN) Resources and Issues
Last night was the inaugural Arizona PowerShell user group meeting known as AZPOSH. There was well over 20 people there and a great guest speaker. Dr. Ferdinand Rios who is the CEO of Sapien Technologies spent an hour talking to us about what is new at Sapien…and wow there is some really cool stuff coming out soon. Dr. Rios is a dynamic presenter and also a coder of some of their products. He showed off an early alpha version of Visual Powershell which is perfect for a person like me that doesn’t like to remember (ok doesn’t have the mental capacity) a bunch of cmdlets and the ability to save portions of code for later use. He also showed iPowerShell which is an app for iPhones as well as the iPad. The future of that app (as long as it gets ported over to other phones) looks amazing. The ability to use a device like the iPhone or iPad to run PowerShell remotely reminds me of the old Star Trek days.
Jason and Mike both did a great job running the meeting and I’m really looking forward to where this user group is going. I know they are working on opening this up to a remote audience as well which is really intriguing for people that aren’t in the Phoenix area but still want to be part of the PowerShell community. Jason suckered me in to presenting for the July meeting…actually I’m really excited to be able to speak about Active Directory and PowerShell. Can’t wait to attend the next month’s meeting!!!
I’m a huge fan of Windows 7. I love just about everything with it. There is one feature that I seem to always fight with and that is Windows Shake. Take a look here if you are not familiar with this feature. Most people like it, perhaps I just shake a bit to much! If you’re like me and you want to disable this feature follow the steps below to edit the registry to do so.
- From the Start Menu Search or Run dialog box type Regedit (depending on your UAC configuration you may have click Yes to open it)
- Navigate to the following key - HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows
- Right-click on Windows key and create a new key called Explorer
- Right-Click on the Explorer folder you just created and create a new DWORD (32-bit) Value key (even if you have installed the 64bit version of Win7)
- Name the DWORD – NoWindowMinimizingShortcuts
- Assign it a value of 1
- Close Regedit
- Log off and log back on to have the key take affect.
I’m sure you are like me when it comes to locking your desktop. You ALWAYS do it. Most if not all corporations today have a group policy in place that at least sets the Screen Saver on after a certain amount of time and requires a password for security reasons (User Configuration - Administrative Templates - Control Panel – Personalization – Password protect the screen saver).
You know as well as I do that there is always that one person that seems to always forget to lock their workstation. Sure the group policy will kick in…eventually. During that time the system is unlocked and the data vulnerable.
Since i’m such a huge fan of shortcuts I have two for the price of one today. I will show you two methods to lock your workstation…even for those very forgetful people.
Method 1 (and what I think is the easiest)
By pressing the Windows key and L on the keyboard you effectively lock the system. I use this one ALL the time. It is the quickest method that I know. However some people are not so keyboard shortcut friendly.
For the people that prefer to use their mouse here are several steps to create a desktop shortcut. This method is very similar to the post I had on creating a shortcut for the Network Properties in Server 2008.
1. From where ever you want the shortcut create, Right click and select New –> Shortcut (I recommend the Desktop)
2. Put the following path into location rundll32.exe user32.dll,LockWorkStation
3. Click Next and type whatever you would like the name of the Shortcut Icon to appear as and click Finish.
4. Time to change the way the Icon looks - Right Click on the newly created Shortcut and select Properties
5. Click the Change Icon… button and change the path to %SystemRoot%\system32\SHELL32.dll and now pick whichever Icon you prefer.
6. We finally have an icon available to lock the workstation on the Desktop.
I personally love when people at work leave their workstations unlocked. Like a lot of you i’m sure you like to teach that person a lesson. Perhaps mess with the background…a nice screensaver message on how much they look up to me!
I’d like to share some of the things I look at while do a health check on a server. Its funny how few resources there are out there on the Internet. I believe people keep this kind of stuff to them self because they are scared they are going to miss something and they will never live it down. My response to that is, So What! Heck, I don’t claim to know it all but why not share what I do know and maybe others can share via the Comments!!!
When I’m troubleshooting I like to compartmentalize what I'm looking for. With that my health checks are set up the same way. I also believe health checks are quick snapshots of the health of a server. Sure there are tools that you can use to analyze systems further but in this case we are doing a quick health check. Not all of these need to be done but some should, you get to decide.
Occasional high CPU spikes are ok as long as you are aware of the process causing this. A server should maintain 80% CPU utilization for an extended period of time. If it does it may be time to upgrade. Its a good idea to keep Task Manager open during the duration of your troubleshooting to see trends.
Check CPU Usage
Open Task Manager
Check the Processes tab, ensure there are no processes consuming excessive CPU
Check the Performance tab, ensure there are no single CPU’s that have excessive CPU usage
Check CPU HW
Open Device Manager (right click computer –> Manage)
Ensure that no CPU’s have red X or yellow ! underneath the Processors
This is one area that you may not want to do for quick health checks but is something you should be familiar with. Task Manager only gives you basic info on processes and you will find that you may need to dig a bit deeper. For that I recommend Process Monitor from the great SysInternal tools. Process Explorer can also be used. In fact download and play with all these tools…they will save your bacon, I guarantee it.
Copy Process Monitor locally, then launch it.
- Analyze each process and watch what operations open the reg keys, file etc.
Copy Process Explorer locally, then launch it.
- Analyze each process based upon the number of threads, handles, loaded DLL’s, etc.
Two great webcasts can be viewed here to see these types of tools in action.
General rule of thumb is to make sure the general memory utilization does not exceed 80%within a given period of time.
Check Memory Availability
- Open Task Manager
Select the Performance tab
Look at the Physical memory box, and multiply the total memory by .2
If the total available memory is less than this number then the box is currently utilizing more than 80 percent of the memory.
Current utilization by process
Select the Process tab
Check the ‘show processes from all users’ box in the bottom left corner
Click the column header ‘Mem Usage’ to sort the processes by memory utilization, highest to lowest. This will help you determine what processes are currently utilizing the memory on the box and can help you narrow your search for memory intensive processes.
Check NIC HW
Verify both ends of the network cable are securely seated in the port
On the back of the server verify you have a green blinking link light on the NIC port
Verify NIC HW is working properly by using Device Manager and ensure the active NICs are showing green
Verify gateway, IP, subnet mask, DNS, DNS suffixes, etc. are properly configured.
If everything is properly configured and HW is working, you should be able to get a ping response from the gateway.
Check Network Connections
Here are some other checks you should perform to ensure proper network connectivity:
ipconfig /all will display all you TCP/IP settings including you MAC address
ipconfig /flushdns will flush your dns resolver cache
ipconfig/displaydns will display what is in your dns name cache
Netstat -an command will show all the connections & ports from a machine
Nbtstat command will show net bios tcp/ip connection stats
Tracert <IP or DNS Name> command will show you the path the packet takes, the routers, and the response time for each hop.
pathping <IP or DNS Name> command combines ping and tracert to the 100th degree. It pings each hop 100 times and is great for testing wan connectivity
All kinds of bad stuff can happen when your disk space is filling up. The best way to alleviate this is to write a script to notify you when you reach a certain threshold. In a future post I'll share a method for you to do just that…however if there is a problem and you need to perform a health check then here is how you check the space the old fashion way.
To check disk space manually:
Right Click on My Computer
Select Disk Management
Validate each disk more than 10 percent free space
Event logs can reveal a more historical perspective on what is going on with the system and applications. Things to look for when troubleshooting event logs is to query either the system or the application logs and look for the presence of events that have a timestamp near the time of the issue you are troubleshooting.
Events have 3 categories in the event viewer:
Warning: Noted with a yellow icon and exclamation point. These usually are looked up as they serve as predictive future failure indicators, such as disk space running low, dhcp ip address lease renewal failures, etc.
Error: Noted with a red circle icon and ‘x’. These are indications that something has failed outright and are a good starting point for troubleshooting.
When looking at event logs, use the information to determine the following:
Also make sure you take a look at eventcombmt from Microsoft. This tool allows you to search the logs of multiple machines. The benefit to this is to see if a specific error or warning message is also occurring on other systems. This can help rule out issues.
Troubleshooting services should be limited to the specific that is affected by the problem being troubleshot. Each server will have specific services varying upon the types of applications running. You should document how your servers services are configured to and compare that to the server in question to see if anything is not configured correctly.
Servers that host applications and services that require high availability should be clustered so that if one node fails the other can pick up the workload. Clustered servers need the same type of health checks as stand-alone systems except you will want to check on the health of the cluster.
Check Cluster Resource Status
Open Cluster Administrator: Log onto server, select Start –> Run –> cluadmin
Check the Resources and ensure all are Online
If Cluster Administrator does not open, ensure that the Cluster Service is running on the node.
Cluster resource status can also be checked from a remote server. From a command prompt, just type - cluster res <cluster name>
Client Side Health
Right click on My Computer, select Manage
Open Device Manage
Drill down to SCSI and RAID Controllers, verify that the HBA HW is visible and does not show any errors
If it does not show up in Device Manager, you may need to re-scan for the HW, re-seat the fiber card, or re-install the driver.
If the HBA is showing healthy in Device Manager, open the tool that you use to view configuration and settings for the fiber card and verify there aren’t any transmit/receive errors on link statistics or counters
Make sure fiber is properly connected to each switch
Make sure switch has no errors
If you’re using zoning verify it is properly configured
Check Fiber and SAN Connectivity
Log onto san appliance and verify that the SAN is in general good health and no major errors are present for the controllers, loops, switches, or ports.
Ensure that the LUNs are presented to the servers in the cluster
Some applications will require you to spread the load across multiple servers. Web servers are a very popular choice to network load balance. As with clusters we will need to check the status of the load balancing.
Check NLBS Status CMD Line
From a command prompt on the local system, run ‘wlbs query’. This will give you the convergence status of the local node with the nlbs cluster.
Other useful NLBS commands: wlbs stop (stops nlbs), wlbs start (starts nlbs), wlbs drainstop (drains node)
Check NLBS Configurations
Open up the network properties –> Network Load Balancing, right click & select Properties
On the Cluster Parameters tab, verify that the IP address is configured for the shared NLBS IP and that the subnet mask, domain, and operation mode are configured correct1y.
On the Host Paramters tab, make sure each node of the cluster has a unique host identifier. Also verify the IP and subnet mask are configured for the local values.
Also make sure that your switch has a static ARP entry if using multi-cast NLBS. The entry should be that of the virtual MAC of the cluster. To get the virtual MAC of the cluster, you can run the following command: WLBS IP2MAC <virtual IP address>
To healthcheck name resolution, open a command prompt and enter the following
Verify that the servername is correctly entered in DNS
If a record does not show up in the DNS query, or maps to a different name, perform a reverse lookup by IP address to see what name is associated with the IP address * nslookup <IP address>
If no name shows up associated with the IP address, log into the domain controller and check the DNS records for this particular name/ip address
From a Domain Controller go to start–>run–>dnsmgmt.msc
Expand the Forward Lookup Zones
Expand the zone for you primary zone that holds the records for the system/s you are troubleshooting
Validate that the record exists. If it does not exist manually enter the record name and IP address by right clicking on this same zone,
Select new host (a)
Enter the name and IP address
Check the box next to Create associated pointer (PTR) record
Click add Host
Additionally log back into the node that you manually entered the record for and ensure that DNS is registering in DNS
Right click on the My Network Places icon on the desktop and select Properties
Double click on the primary adapter
Highlight internet protocol (TCP/IP) and select properties
Validate the IP addresses of the DNS servers are correct
Select DNS tab
Make sure the box is checked next to Register this connection’s address in DNS
As I wrap this up I realize there is so much more that can be done. Each application type of server needs its own set off health checks. For example web servers, terminal servers and database servers. Remember this is just the baseline for each server and that other components can and should be layered on top of it. Again I would love to hear from others so please feel free to add you comments below.
If you have been playing with the the AD PowerShell cmdlets you know that it requires a few things to run, first Windows Server 2008 R2 or Windows 7, the .NET Framework 3.5.1 and of course if you want to manage an AD domain you need Active Directory Web Services (ADWS) installed on at least one domain controller.
By the way ADWS requires TCP port 9389
So how in the world does a Windows 7 system know how to find a DC running ADWS? Well your client running PowerShell will use the normal DC locator process. First the client will determine which site it is in nltest /dsgetsite and then it will determine the closest DC nltest /dsgetdc:<FQDN Domain>. It is looking at the DC for the following flag:
More info on that flag can be found here.
Now what if you don’t have Server 2008 R2 DCs? With Server 2003 and Server 2008 a problem occurs because the Net Logon service of those domain controllers does not recognize the DS_WEB_SERVICE_REQUIRED flag. There are two hotfixes (one for what ever version of AD you are running) available to fix that in those environments. Server 2003 and Server 2008
After you install this hotfix the AD PowerShell module and Active Directory Administrative Center will be able to locate DCs that have Active Directory Management Gateway Service installed, similar to Active Directory Web Services (ADWS) on a Windows Server 2008 R2-based computer.
UPDATE - Microsoft appears to have taken this download down. No word why or when it will be back up.
Looks like Microsoft just make the Windows 7 LDS (Lightweight Directory Services) client available. You can find both 32 and 64 bit clients here.
For those that aren't familiar with LDS, it is the Server 2008 replacement for ADAM, otherwise known as Active Directory Application Mode. While i'm no developer LDS is a good platform that applications that require directory storage and access. Have most of the components of Active Directory without the complete infrastructure needed for Active Directory.
More Posts Next page »