Tuesday, 14 July 2015

#WAP - Remove Web Application Proxy (WAP) from Cluster - Windows 2012 R2 (ADFS)

Example:

WAP Cluster with 2 ADFS Proxy. To remove ADFS-Proxy1. 

Solution:

1. On one of the ADFS Proxy server, run PowerShell with Administrator.
2. Enter Command below:

swpc -ConnectedServersName ((gwpc).ConnectedServersName -ne 'adfsservername')


3. ADFS-Proxy1 removed.


Reference:




http://blogs.technet.com/b/applicationproxyblog/archive/2014/08/20/web-application-proxy-powershell-cheat-sheet.aspx


Friday, 10 July 2015

#AS FS proxy- could not be configured

An error occurred when attempting to establish a trust relationship with the federation service. Error: Unable to connect to the remote server.


Solution:

1. Make sure Federation Name able to resolve from ADFS proxy server.
2. ADFS and ADFS Proxy server able to ping each other.




#AD FS - Error. Event ID 364

Error:

An error occurred. Contact you administrator for more information.

Microsoft.IdentityServer.RequestFailedException: MSIS7065: There are no registered protocol handlers on path /adfs/ls/idpinititedsignon.aspx to process the incoming request.





Solution:

1. Launch ADFS Management.
2. Right Click on Authentication Policies, select Edit Global Primary Authentication.

3.On Intranet, uncheck Windows Authentication, select Forms Authentication.

4. Restart ADFS server.
** Try to use firefox or google chrome to test https://sts.domainname/adfs/ls/idpinitiatedsignon.aspx
** Try to log in "https://sts.domainname/adfs/ls/idpinitiatedsignon.aspx" from another computer
** Make sure the address is correct. 
** Wait for 10-20 minutes and restart adfs server again.

It should work. Personally test many times.

Drop me an email if not work.
Email: darrenong877@gmail.com



#AD FS - Connect-MsolService Fail / Unable to connect Azure via Windows Azure Active Directory Module PowerShell

Error when connect-MsolService

Cause:

1. Firewall, proxy server block.
2. Microsoft Online Service Sign-in Assistant version.
3. Windows Azure Active Directory Module for PowerShell version.

Solution:

Reinstall Microsoft Online Service Sign-in Assistant and Windows Azure Active Directory Module for PowerShell.

Recommended Version for:

Microsoft Online Service Sign-in Assistant version: 7.250.4556.0
Version can check via regedit. (HKEY_Local_Machine\Software\Microsoft\MSOIdentityCRL\MSOIDCRLVersion)

Windows Azure Active Directory Module for PowerShell version: 1.0.8070.2 and above
Version can check via Azure PowerShell.
(get-item c:\windows\System32\WindowsPowerShell\v1.0\Modules\MSOnline\Microsoft.online.administration.Automation.PSModule.dll).VersionInfo.FileVersion



Can download from here:

Download here

Download here

Tuesday, 7 July 2015

#AD FS - Can't install Windows Azure Active Directory Module for Windows PowerShell

In order to install Windows Azure Directory Module for Windows PowerShell, you must have Microsoft Online Services Sign-in Assistant version 7.0 or greater installed on this computer.



Cause:


.NET Framework 3.5 Features.

Solution (Method 2 preferable) 

Method 1:
  1. Go to regedit, navigate to HKEY_Local_Machine\Software\Microsoft\MSOIdentityCRL
  2. Double click on MSOIDCRLVersion, change value from 7.250.4303.0 to 7.250.4551.0
  3. Install Windows Azure Directory Module.
  4. Change back the value from 7.250.4551.0 to 7.250.4303.0
  5. Restart Computer.
Method 2:

http://ms.darrenongpt.com/2015/07/connect-msolservice-fail-unable-to.html

Monday, 29 June 2015

#O365 - Create Microsoft O365 Office ProPlus Offline Installer

1.    Office Deployment Tool

1.1.  Download Office Deployment Tool

1.2.  Install Office Deployment Tool

a)      Create 2 new folders on C: drive. Name it as O365 Pro Plus_32 and O365 Pro Plus_64
b)      Run the office deployment tool.
c)       Accept the Microsoft Software License Terms.
d)      Extract to C:\O365 Pro Plus_32                                   
     


1.3.  Edit Configuration.xml file

a)      Open C:\Office Pro Plus_32\configuration.xml
b)      Edit the file as below. <Configuration>

<Configuration>
  <Add OfficeClientEdition="64" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Updates Enabled="TRUE" />
  <Display Level="None" AcceptEULA="TRUE" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

** If 64 bit, change <Add OfficeClientEdition="32" > to <Add OfficeClientEdition="64" >

2.    Microsoft O365 Pro Plus Installer

2.1.  Download the Installer

a)      Open Command Prompt, run the command as below:
setup.exe /download configuration.xml
b)      An office folder will created automatically. (It will take few minutes to hours to complete. Office -32 about 0.9GB, Office 64-bit about 1.1 GB)
c)       Once completed, you will have the content as below. 

2.2.  Installation

a)      Create a .bat in same directory with where you extract the office deployment tool.
   
b)      Content of .Bat file as below:
c)   Run the .BAT file.

Friday, 19 June 2015

#Windows Server 2012 - How to add other workgroup server manage in server manager

Fail to add workgroup server to server manager.

Error: Configuration refresh failed with the following error. The metadata failed to be retrived from the server due to the following error: WinRM cannot process the request. The following error occurred while using Kerberos authentication. Cannot find the computer servername. Verify that the computer exist on the network and that the name provided is spelled correctly.


Solution:

1. Login to the management server.
2. Run the Windows Powershell as Administrator.
3. Type:

  • Set-Item wsman:\localhost\Client\TrustedHosts Servername -Concatenate -Force.


4. Open Server Manager, select Add other servers to manage.

5.  Select DNS, and then enter the server name/IP that you want to manage. Click to add the server.