Archive

Archive for the ‘Uncategorized’ Category

Switch to Office 365 from Google G Suite

hey !!!

Are you or your company switching to Microsoft Office 365? Microsoft have your go-to guides to help you get up and running in Office 365 with minimum disruption. We have 8 published today for Word, Outlook, Excel, PowerPoint, and OneDrive, with more on the way.

have a great On-boarding 🙂

Categories: Office 365, Uncategorized

Meet innovators and explore tomorrow’s tech at Microsoft Ignite 2017

Microsoft Ignite 2017 is around the corner and you can Join us at Microsoft Ignite! Connect with your community, choose from over 900 sessions, and explore new tools and tech.

Go Here for registration

Also you can Sway your boss using email template 🙂

Unable to create CMS database for the Lync FE pool Error “Install-CsDatabase : Command execution failed: The requested object does not exist. “

We were in transition phase to move CMS database from lync 2010 to Lync 2013 server. All users were migrated and now migrating CMS.

Lync 2010 Environment:

Lync 2010 Front End Pool contain two front end servers and one of the front end server is CMS master Server. This pool has one standalone SQL server which is holding CMS database along with other database.

Lync 2013 Environment:

Lync 2013 have three front end servers. This front end pool have two node cluster SQL which is holding backend datasbe for this pool. Backend SQL cluster is also holding instance for one other front end pool called “BIG Meeting”.

 Problem :
As per MS article we issues the below command to create the new Central Management store database in the Lync Server 2013 SQL Server database which is a prereqsuite to start the CMS realocation

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn “FQDN SQLInstance” -SqlInstanceName “SQLInstance”

Above command failed with below error

Install-CsDatabase : Command execution failed: The requested object does not exist. (Exception from HRESULT: 0x80010114)”

Solution: As we have SQL cluster hosting all lync 2013 BE instance, we must use database and log file path to tell the cmdlets to create CMS database.

Then we used a command as below with ‘DatabasePaths’ switch.

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn “FQDN SQLInstance” -SqlInstanceName “SQLInstance” -DatabasePaths “E:\CSLog”,”F:\CSLog”,”G:\CSDB”

This command was able to successfully created the xds database.

We also move the CMS from Lync 2010 to Lync server 2013 pool, it was completed successfully.

Hope it will help others hosting Lync 2010/2013 database in SQL cluster form 🙂 !!!

 Reference :

Install-CsDatabase

https://technet.microsoft.com/en-us/library/gg399044.aspx

Configure SQL Server clustering for Lync Server 2013

https://technet.microsoft.com/en-us/library/dn383982.aspx

Database installation using Lync Server Management Shell in Lync Server 2013

https://technet.microsoft.com/en-us/library/gg398832.aspx

 

Categories: Lync 2013, Uncategorized

Failed to save Web Ticket Signing certificate to the file store

Issue : Lync mobile client can not sign-in .

During my troubleshooting on my lync director server, I see Event 4101 which indicating “Certificate file path” can not be  found. I tried to browse the File store asscitae with DIR servers and can not browse. So its confirm that problem is occurring due to store only. You can also see this event if you have permission problem on lync store directory.

WebTicket

Worked with Storage admin to enable the lyncShare directory with old data which resolved the issue.

Categories: Lync 2013, Uncategorized

Lync 2013 Edge server installation failed on partial installation – Error (An error occurred while applying SQL script for the feature RTCdatabaseStore)

April 29, 2014 3 comments

Many of us would have fall under such situation when you are trying to install Lync 2013 Edge serer role again on any previous failed installation. So what happened. In the previous installation, Lync 2013 setup created RTCdatabase instance which may failed to rewrite while you again run the setup.

We have been seen this issue in one of the EDGE server located in Lync LAB and fixed it by remove old RTC instances and reran setup again

1: Below screen show that Lync 2013 edge setup is failed and not able apply SQL script for the feature RTCDatabaSstore.

1

2: We tried to connect SQL instance of Edge server from one of the SQL backed console using “SQL Management Studio” and deleted them one by one.

2

3:   I understand that in production environment you can not connect edge server from internal SQL server as its sit in   perimeter network. So you can install one dummy SQL server in same Subnet where Edge server is localized and remove the RTC local database.

3

4: Run the setup again from lync 2013 deployment wizard which would go smoothly.

4

I hope it could help someone have faced such issue 🙂 🙂  !!!!

Writer : Amit Shah (Lync Expert)

Team (MessagingSchool)

Categories: Uncategorized

Attractions in 2013 on this Blog !!!

January 18, 2014 Leave a comment

The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.

Here’s an excerpt:

The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 23,000 times in 2013. If it were a concert at Sydney Opera House, it would take about 9 sold-out performances for that many people to see it.

Click here to see the complete report.

Categories: Uncategorized

A myth – Removing GC/DC and Exchange CRY

September 9, 2013 Leave a comment

In the weekend I was working with my friend and helping him to remove his existing GC/DC and seen some interesting behavior about exchange which I thought to admit here which may be benefit to people those stuck into such Environment.

Current Setup

The environment has only one windows 2008 Server with all FSMO role installed and on top of that Exchange 2010 CAS,MBX,HUB role also installed (I know it’s not recommended 🙂 )

Requirement

They had installed one Exchange 2010 SP2 on Windows 2008 R2 server and configure all the roles and migrated all Mailbox, public folder etc. to new server successfully.

Installed one new DC (Windows 2008) and configured this DC as GC replicated DNS. All seems working fine on new DC as expected.

Now real fun is going to start. If you see various blog post and TechNet forum discussion, lots of MVP and expert advice to use CMDLET “Set-ExchangeServer” and point new DC/GC as static. I agree its good cmdlet and help Exchange Administrator to avoid any down time while you ask exchange to talk with new DC/GC

BUT, What about if someone change DC/GC for whatever reason – it becomes unavailable for an extended period of time (or worse: someone decided to decommission the server without telling you (happens all the time!). This would cause the Exchange Server to try binding to a non-existing DC/GC. Again if you want to remove static entry you can’t do as EMS is not getting started.

To avoid such issue and let exchange connect itself new DC/GC you need to allowing exchange minimum 30-45 minutes time. In this duration lots of event will generated as below.

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1111).
Exchange Active Directory Provider will discover the new DC’s and will show in in event log (Event id : 2080) . Let concentrate the event now.

(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
DC-OLD.ABC.local CDG 1 7 7 1 0 1 1 7 1
DC01.ABC.local CDG 1 7 7 1 0 1 1 7 1

If you see above the SACL value of both DC is ‘1’ which indicates that both DC’s are working as GC’s now. Now it’s time to shutdown/Disconnect old DC from network. Wait for 30 minutes and observe event logs. Go exchange server and try to restart Exchange AD topology server which would stop all services one by one and then start it again. Once all service are started , now you can confirm that new exchange is talking with new DC.

Now wait for couple of days and proceed with exchange & DC/GC removal.

Note : in some cases it has been observers that SACL value is  not showing 1 for new DC which cause exchnage to down. To resolve this. In the Default Domain Controller policy AND the Default Domain Policy under Windows Settings –> Security Settings –> Local Policies –> User Rights Assignment, the policy “Manage auditing and security log” must have the Exchange Servers group added. This was not added in this environment. Once this was added the SACL as above changed to “1″ and the Exchange services started correctly

So, Why Set-exchangeServer cmdlet 🙂