Who's Online
6 visitors online now
2 guests, 4 bots, 0 members
Support my Sponsor
  • An error has occurred, which probably means the feed is down. Try again later.

Posts Tagged ‘Active directory’

Creating a Lab on Windows Azure – Install SQL, SharePoint. etc. labs as part of this domain

  • Install SQL, SharePoint. etc. labs as part of this domain

Once we are confirmed using script we are able to add new Virtual Machine to domain, we can use the ready to use SharePoint, SQL, etc. VM’s as part of our Lab environment. Let’s see an example of SharePoint server.

  1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
  2. Select “Virtual Machines” from left menu and select “Create a Virtual Machine”

0148

  1. Under “Virtual Machine” select “From Gallery”

0149

  1. On the Choose an Image screen select SharePoint server 2013 Trial. This trial works for 180 days.

0159

  1. Type the Machines necessary details like Hardware configuration, Machine name, username and password
  2. Now we have an important step in the process. Select the DEMONETWORK you created in Region/Affinity Group/Virtual Network. Make sure our Virtual network name is selected in Virtual Network Subnet. Click on Next

0156

  1. Now comes the most important step, we need to select Custom Script on this page and select the Join.ps1 script we just created. Click Finish

0157

  1. Now you can see that even SharePoint server is ready within few minutes
  2. Advantage here is that you have a single credential stored on Active directory using which you manage all the Virtual Machine and work on your lab.
  3. Below you can see that I have created SQL server, SharePoint server and started using them in just couple of minutes.

Creating a Lab on Windows Azure – When creating a new server it should be part of this domain

We are nearly done with our Domain related activities. Now we need to make sure that all the Virtual Machines we create are part of same Active Directory. This will help us to manage the server and users in domain. In number of Demos we need a domain (AD), so we have met the most important pre-requisites.

 

  1. You need to copy below script into a notepad and save it as join.PS1

///// SCRIPT START HERE   ////

 

$domainName = “type domain name here e.g. demo.com. It should be in quotes”

$username = “type domain\username e.g. demo\user1. It should be in quotes”

$password = “type password of above user e.g. 213@jjj. It should be in quotes”

$securePass =  ConvertTo-SecureString $password -AsPlainText -Force

$cred = New-Object System.Management.Automation.PSCredential($username, $securePass)

Add-Computer -DomainName $domainName -Credential $cred -Restart –Force

////// SCRIPT END HERE   ////

 

  1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
  2. Select “Virtual Machines” from left menu and select “Create a Virtual Machine”

0148

  1. Under “Virtual Machine” select “From Gallery”

0149

  1. On the Choose an Image screen select “Windows server 2012 R2” and select Next
  2. Type the Machines necessary details like Hardware configuration, Machine name, username and password

0150

  1. Now we have an important step in the process. Select the DEMONETWORK you created in Region/Affinity Group/Virtual Network. Make sure our Virtual network name is selected in Virtual Network Subnet. Click on Next

0155

  1. Now comes the most important step, we need to select Custom Script on this page and select the Join.ps1 script we just created. Click Finish

0156

  1. You will observer that your machine will reboot during the initialization process.
  2. Now when the machine is created, Open Server Manager and you will observe it is already part of Demo domain. On the domain controller in “Active Directory users and computers” you should be able to see the newly added

 

Note: In some rare scenario, the new computer may not get added to the domain. In that case, please run above PowerShell command line by line and the computer would be added to domain.

Create a Active Directory Forest on a Windows Azure VM

  • Create a new domain

Now let’s configure this server to be a Domain Controller. As discussed earlier Domain controller manage DNS, AD Users, etc. and are normally the 1st and most important server in a company.

 

  1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
  2. Select Virtual Machine from left Menu
  3. Select the Virtual Machine we just created and click on Connect at bottom
  4. Now RDP to the Virtual Machine we created and click on Server Manager

0123

  1. Select Manager > Add Roles and Features

0124

  1. Select “Next” on Installation Type screen

0125

  1. Select “Next” on Destination Server screen

0126

  1. Check Box “Active Directory Domain servers”

0127

  1. Click on “Add Feature” on pop-up screen

0128

  1. Select the check box “Restart the destination server if required” > Click OK

0129

  1. Once it is installed, Click on Close

0130

  1. Open the Server Manager again, Click on Flag at top and select “Promote this server to a Domain Controller”

0131

  1. Select “Add a New forest”, type domain name
  2. Type the DSRM password and click “Next” (Note: this is required when you try to recover your active directory)

0132

  1. Now you will have to select your domain name. For example. Demo.com
  2. The NetBIOS Name screen will remove .com and you will see only demo.
  3. Select the Default location of installation and click “Next”
  4. Click on “Install”

0133

  1. Once the Computer is restarted, your Domain Controller would be ready.

Note: From now on when you logon to server you need use your domain name along with username we just created to authenticate to server. Example: demo\user1

Active directory groups are missing in SharePoint User Profile service application

I have seen a lot of post which says they have configured User Profile Service application to import users and groups from Active Directory. User are successfully imported and Active directory groups are not getting imported by the User Profile Service application.

Probably the groups are being imported (these are required by things such as audiences). They will not be displayed however in manage user profiles (or anywhere else), this is by design. Try creating an audience based on group membership and compiling it, this will prove if the groups are imported or not.

You can still check Active directory groups in miisclient tool at, for SharePoint 2013 it is 15.0 instead of 14.0:
C:\Program Files\Common Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe

  1. Run the MIISclient.exe as Administrator
    0109

 

  1. Click on the Management Agents button on the top menu bar
  2. Right-click on “Active Directory Connector” and choose Run from the context menu.
    0110

  3. Highlight “Full Import Full Sync” and choose OK.
    0111

  4. The State will change to Running. The bottom half the screen will give information on any changes that it makes during the run as well as any errors encountered.
    0112

 

Here you would be able to see the number of groups imported

 

Also check below Articles:

http://technet.microsoft.com/en-us/library/cc262327.aspx

http://technet.microsoft.com/en-us/library/ee721054.aspx