Active Directory

Tech Short: Using PowerShell to join Computer to AD Domain

Working on a server installation I decided to use a simple yet effective power-shell command to join a Windows Server 2012/R2 system to our domain.

For the sake of brevity lets just show you.

Requirements:

  • Admin access to the computer/server you are joining to the domain along with permissions in the AD domain to join machines
  • Connected to the network where the domain is accessible
  • Obtain an network ip address along with dns that can resolve the domain you are joining
  • PowerShell

Steps:

  1. Launch PowerShell as an Administrator
  2. Issue the following command example: Add-Computer -DomainName <domain name> -Restart

You will be prompt for a username and password at this point. Enter in the correct credentials and soon after a restart will occur.

When you resume from the restart you can now log in on this workstation/server with domain credentials.

Additional info can be found on Technet

I hope you enjoyed this short, thanks for visiting – jermal

Remote Server Administration Tools for Windows 10 | Released

Weeks of waiting and its here at last.

Q. What is it?

A. RSAT (Remote Server Administration Tools) is a Windows Server component for remote management of other computers and server operating systems running Windows.

Grab the tools here: Remote Server Administration Tools for Windows 10

 

Tech Short Q&A: What is vCenter Single Sign-On For

What is vCenter Single Sign-On?

vCenter Single Sign-On is a feature of VMware vCenter 5, 6 and future vCenter implementations that is an authentication broker which also creates security tokens providing a secure way of accessing your environments.

This token exchange mechanism is far superior than the former requirement of each component authenticating separately with a directory service such as Active Directory. Its VMware’s answer to identity management

Here are some key capabilities of SSO?

  • add multiple AD domains, OpenLDAP, and the local operating system where SSO is deployed. It also lets you create local users and groups.
  • allows VMware vSphere to connect to a non-AD Identity Source, OpenLDAP.
  • supports the SAML 2.0 standard and WS-TRUST, both of which are open industry standards.
  • lets users delegate tasks to solutions that can run as the identity of the user.
  • supports identity delegation for long-lived tasks with the ability to renew tokens.

follow this link -> VMware vCenter Single Sigion-On for more info on

 

I hope you enjoyed this techshort, thanks for visiting – jermal

Tech Short: PowerShell to list users in AD security group

You want to get a list of users who exist as members of a AD (Active Directory) security group. Here are some quick steps on accomplishing this task.

Lets begin:

  1. Open PowerShell or PowerShell ISE
  2. Type Import-Module ActiveDirectory
  3. Followed by Get-ADGroupMember -identity “Group Name” | select name | Out-GridView

And there you go, fast and simple to do.

 

Remove Dead Exchange Servers from Active Directory

Working with  my Exchange 2012 Hybrid configuration I into the following error:

ERROR : Subtask NeedsConfiguration execution failed: Configure MRS Proxy Settings

Execution of the Get-WebServicesVirtualDirectory cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings.

The task wasn’t able to connect to IIS on the server ‘exchange’. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.

This is because I did not properly remove the retired exchange servers form Active Directory during past migrations to Exchange 2013.

To remove these objects to continue with your Hybrid configuration task do the following:

  1. Launch the run dialog (Windows Key + R)
  2. Type in the command “adsiedit.msc” and press OK
  3. In the drop down menu select “Configuration”
  4. Expand “CN=Configuration [domain]\CN=Services\CN=Microsoft Exchange\CN=[organization]\CN=Administrative Groups\CN=Servers”
  5. Right click on the dead server and “Delete”
  6. Navigate to ”CN=Configuration [domain]\CN=Services\CN=Microsoft Exchange\CN=[organization]\CN=Administrative Groups\CN=Databases”
  7. Right click on each dead database and “Delete”

Step 1-5 will get you past the Hybrid error, but you might as well cleanup while your here.