Collab365 Summit - May 10th-12th 2016 - Live from Microsoft HQ

Collab365 Summit - May 10th-12th 2016 - Live from Microsoft HQ

Register yourself @ Collab365 Summit 2016

In the Collab365 team on the 10th, 11th and 12th of May 2016 for an incredible amount of SharePoint, Azure and Office365 content. Delivered direct to your device, when you want it and for no cost at all. Catch premium keynotes across all 3 days. Sessions designed and delivered for IT Pro, IT Dev and Business delegates.

Introducing brand new Summit Experience for 2016

Watch Live

Watch the LIVE SHOW streamed direct from Redmond or catch the recorded sessions from top speakers around the world. If you are a seasoned pro or just starting out on your career with SharePoint and Office 365 we have plenty to help you begin your skills journey 

Learn Lost

100 sessions of amazing content brought to you by Microsoft - Direct from MS HQ and beyond, community experts and evangelists from right around the globe. Watch Dev sessions, IT Pro and Business sessions. It's all free to attend and is guaranteed to educate.

Have Fun

As well as live sessions, live chat and real time twitter feeds, we have been adding more spice to the mix in the form of 2 real-time, tech based, fun as heck quizzes. Compete against your peers, win prizes and unlock new learning opportunities!

Microsoft Product team speakers

Bill Baer and Raman Sharma	SharePoint
Jeremy Thake	Office 365 – Product Manager
Sonya Koptyev	Office 365 – Product Manager
Mark Kashman	Office 365 – Product Manager
Chris McNulty	Office 365 – Product Manager
Reuben Krippner	Office 365 - Director
Christophe Fiessinger	Enterprise Social Group

SharePoint Farm configure in Azure

When I was trying to configure the SharePoint farm in Windows Azure, I often encountered this problem.

My SharePoint farm consists of Domain Controller , two WFE and one SQL Server.

I have create the Azure Virtual Network and all of the above VMs are connected in the same sub net.

Still the server manager reports this below problem and subsequently I am not able to connect the VMs in to Domain Controller.

When I am trying to make the WFE-1 as member of Domain controller,It was not able to connect the DC even though virtual network listing all VMs are part of it and shows this error.


WinRM cannot complete the operation.Verify that the specified computer name is valid,that the computer is accessible over the network and that a firewall exception for the WinRM service is enable and allows access from this computer. By default,the WinRM firewall exception for public profiles limits access to remote computers within the same local sub net.

To identify this problem and resolve, I searched through on windows azure forums and discussion and come up with resolution. Eariler I joined the WFE-1 with the domain controller by choosing the computer name (Murugesan-SP) instead of DNS or fully qualified name and then ran the winrm quickconfig on the same VM and reboot the server and the problem got solved. Now my VMs are connected with DC. 

And also the member computer was created before the VM which was promoted to domain controller that's why DC is not recognize the member computer and WinRM service also not started automatically on the member computer.

When you are joining to DC, always use the DNS name instead of computer name and restart the member computer.

After ran the command , all of the VMs are connected and joined happily with DC.

Topic related video