Q: In AD FS, do you need to purchase additional CALs?

AD FS (Active Directory Federated Services) allow you to provide single sign on (SSO) capability to your business partners. You, as the resource organization, control the access. Your partner organization (or account organization) controls the accounts. That way the user management is not with you, but security is. The users of the partner organization can get access to your resources without creating new user accounts and passwords.

The question of licensing comes into play. Microsoft that a licensing option called External Connector or EC license. This option allows you to provide access to your Windows Server 2000/2003/2008 environments to users who are part of a partner organization and access your resources remotely. You can also utilize a standards Server 2008 CAL for this.

I still recommend talking with a Microsoft Licensing Specialist to best determine the licensing model for your organization.

External Connector license overview.
http://www.microsoft.com/windowsserver2008/en/us/external-connectors.aspx

Licensing overview qith links to people who can help.
http://www.microsoft.com/windowsserver2008/en/us/how-to-buy.aspx

External Connector license overview.
http://www.microsoft.com/windowsserver2008/en/us/external-connectors.aspx

Licensing overview qith links to people who can help.
http://www.microsoft.com/windowsserver2008/en/us/how-to-buy.aspx

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog