Lync 2013 and Raising Forest/Domain Functional Level?

My current forest and domain functional levels are 2008 R2. I know I can safely upgrade the functional levels in most cases, but I want to specifically know with regards to Lync.
Our entire environment, including Lync, is running on Windows Server 2012 R2. (We have no domain joined clients.) We are running Lync 2013 Standard with all the latest updates.
Can I safely raise the forest and domain functional levels to 2012 R2 without impacting Lync?

Hi,
Yes, you can raise Forest and domain function level to Windows Server 2012 R2 without issue.
After raising Forest\domain function level, the new features that rely on the functional level are generally limited to AD itself. Regardless, changing the Domain or Forest Functional Level should have no impact on an application that depends on
Active Directory.
More details:
http://blogs.technet.com/b/askds/archive/2011/06/14/what-is-the-impact-of-upgrading-the-domain-or-forest-functional-level.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Similar Messages

What is the effect if I Raise my domain functional level to Windows Server 2012 R2 ?

Hi,
my current servers:
Domain Controllers= Windows Server 2012 R2 (current domain functional level is windows 2008 R2)
Mail servers= Exchange 2010 SP3 on Windows 2008 R2
Lync= Lync 2010 on Windows server 2008 R2
What is the effect if I Raise my domain functional level to Windows Server 2012 R2 ?
I am very worried about Exchange & Lync if we do this action
please advice

Do not raise the forest functional level higher if you have or will have any domain controllers running
an earlier version of Windows Server , which is (windows Nt4.0, Window 2000 or windows 2003)
but as a matter of fact I dont see any of those in your network so you can easily upgrade the funtional level without any issues
Listed below link has the table which shows the effects of upgrading the domain functional levels to Windows 2012
http://technet.microsoft.com/en-us/library/understanding-active-directory-functional-levels
http://www.arabitpro.com

Lync 2013 and Sametime Same Domain

Deploying Lync within my Org and unfortunate for us we use sametime.
If the Lync 2013 deployment resides in mycompany.com, and thus is the sip domain. The sametime domain is also mycompany.com as this is historic.
Are there any Gotchas or can these both interact as normal using the XMPP Gateway. If you think of it like
[email protected] on lync talking to
[email protected] on sametime, I just wondered if there was any conflicts,
Any documents on setup would also be cool.
thanks

They should be fine independent, but if both need to talk to public XMPP networks, you'll need to pick either Lync or SameTime due to the DNS records for _XMPP-Server._tcp.
If they need to communicate with eachother via XMPP, this would also be difficult because they have the same SIP domain, the routing wouldn't work. They wouldn't know to send the communications via XMPP if they have the same SIP domain.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Raising Domain Functional level

We have 75 domain Controllers in our Org and current Domain Functional level is 2003. We have a mix setup where all versions of OS are available starting from 2003. A large no of applications are also integrated with our current Active Directory.
My concern is, If I raise my Domain Functional level to 2008 then what are the consequences we might face in terms of accessing legacy applications.
Please let me know the checklist which we need to follow and incase of any failure then what will be the rollback procedure.
Looking forward for your valuable inputs.

Hi,
I agree with others. Once the Functional Level has been upgraded, new
servers running on lower versions cannot be added
as Domain Controllers to the domain or forest. If all the DCs in the domain is server 2008 and later version, we can raise the function level of the domain to get more advanced features.
> If I raise my Domain Functional level to 2008 then what are the consequences we might face in terms of accessing legacy applications.
For this question, make sure that the applications in the domain are compatible with the new functional level
For detailed information about how to raise function level, we can refer to the following link:
Raising the Functional Levels
http://technet.microsoft.com/en-us/library/cc771949(v=WS.10).aspx
Best Regards,
Erin

Unable to Raise domain functional level

I am installing a Server 2012 std. in a single domain. The current DC is Server 2008 std. When I try to raise the domain functional level to at least 2003 it gives me an error.
I did the save as and viewed the error message. Apparently some time in the past they had a Server 2000 and active directory still has the entries that is preventing the domain from being raised. I removed the old server from AD CU and restarted
the server. Still will not let me raise the level, same error. Do I need to use ADSI edit and remove all the entries also? What about DNS entries?
Thank you for a rapid answer.
Wade Harris

Hi Wade,
Please refer to following KB and check if can help you. (Please back up before all operations. That will help us to avoid unexpected issues.)
How to remove data in Active Directory after an unsuccessful domain controller demotion
In addition, please also use dcdiag
command-line tool to verify domain controller health.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Domain functional level upgraded to 2008 r2 native mode but query states 2003

Nothing :(

I raised the domain functional level last night to 2008 r2 native mode and after allowing everything to sync i ran the command get-addomain .domainmode and it came back ast windows2003forest.
I dont understand why it is showing up this way, we removed all of the 2003 domain controllers and server from our network before doing this...Any suggestions?
This topic first appeared in the Spiceworks Community

Exchange Server 2003 SP2 - Forest and Domain Functional Level Limitations

Hi All
Bit of a legacy question and theres not much clarity out there..
I need to confirm the highest DFL and FFL Supported by Microsoft for Exchange 2003 SP2?
We currently have a mix of 2003 R2 and 2008 R2 domain controllers with the FFL and DFL currently set at 2003 R2.
The plan is to move to Exchange 2010 in the very near future, so the question is do we need to wait until we upgrade to Exchange 2010 Before upgrading the DFL and FFL to 2008 R2?
From what Ive read we will need to complete the Exchange upgrade first before moving forward with the functional level upgrades..
Thanks in advance
Bull

Hi Bull,
As Ed mentioned, Exchange server 2003 and Exchange 2010 support Windows Server 2003 domain functional level and Windows Server 2003 forest functional level, also supported in higher environment.
More details about it, please refer to “Supported Active Directory environment” section:
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Note that we cannot add new DCs which are the less version of Windows Server
cannot be added to the domain or forest. More details about
the Impact of Upgrading the Domain or Forest Functional Level, for your reference:
http://blogs.technet.com/b/askds/archive/2011/06/14/what-is-the-impact-of-upgrading-the-domain-or-forest-functional-level.aspx
Best Regards,
Allen Wang

Why domain functional level should be greater than or equal to forest FL?

We know that domain functional level must be greater than or equal to forest functional level. Why is that so?
My perspective is if we set FFL to windows server 2008 r2 and DFL to windows 2003, active directory recycle bin won't be available to the domain whose FL is windows 2003. Is that right?

My perspective is if we set FFL to windows server 2008 r2 and DFL to windows 2003, active directory recycle bin won't be available to the domain whose FL is windows 2003. Is that right?
Greetings!
Active Directory Recycle Bin needs to be implemented in a forest with 2008 R2 forest functional level. Because it was added in 2008 R2 operating system. In order to have a 2008 R2 forest functional level you need to raise all the child domains DFL's first.
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Raise domain functional level

Hi All,
What all that need to be considered before raising domain / forest functional level.

Hi channavera,
Some items that you want to consider are what OS are you running for all your DC's in the domain/forest. This is important, since you have to have a certain level for the functional level. For example, if you want to raise up to functional level of 2012,
you will need to make sure any DC's running 2008 or lower are upgraded before you do so. Raising the functional level will change up the schema for the domain, making it incompatible with the lower OS's. If you are going to continue to run 2008
server in the domain/forest, you will want to only raise the functional level to 2008. Also, keep in mind, you cannot go to a lower functional level (i.e. if you go to 2012, you cannot go back to 2008) except under very specific circumstances.
I know what I brought up is not the only consideration, but a big one, as it basically determines what functional level you want to use for the domain/forest.
Also, this technet site goes over what changes for each level. Understanding AD Functional levels

Logon failure after upgrade Windows 2003 domain functional level and schema

Before upgrade:
Windows 2003 Std server: Domain functional level 2000, Schema verion 30
Crystal Report XI R2: Authentication: Windows AD
Logon OK.
After Upgrade:
Windows 2003 Std + Windows 2008: Domain functional level 2003, Schema verion 44
Crystal Report XI R2: Authentication: Windows AD
Logon Error: An error has occurred: java.lan.NullPointerException
Is it a Tomcat problem? OR Java runtime problem? OR XI R2 problem?
Anyone can help to fix it!? Thanks!!

OK, I try again in the testing lab and simplify the combination. We only consider Windows 2003 ONLY.
Before AD upgrade:
AD/Domain Controller: Windows 2003 Std server: Domain functional level 2000, Schema verion 30
Crystal Report XI R2: run on Windows 2003 memeber server
Operating OS: Windows XP/Vista/7: Authentication: Windows AD
Logon OK.
Upgrade cmbination 1
Step 1:
Upgrade Domain controller: Windows 2003 to Windows 2003 R2 (Domain functional level 2000, Schema verion 31 )
Crystal Report XI R2: run on Windows 2003 memeber server
Operating OS: Windows XP/Vista/7: Authentication: Windows AD
Logon OK.
Step 2:
Upgrade Domain Functional Level: Windows 2003 R2 (Domain functional level 2003, Schema verion 31)
Crystal Report XI R2: run on Windows 2003 memeber server
Operating OS: Windows XP/Vista/7: Authentication: Windows AD
Logon Fail
Logon Error: An error has occurred: java.lan.NullPointerException
Upgrade combination 2
Direct upgrade Domain Functional Level: Windows 2003 (Domain functional level 2003, Schema verion 30)
Crystal Report XI R2: run on Windows 2003 memeber server
Operating OS: Windows XP/Vista/7: Authentication: Windows AD
Logon Fail
Logon Error: An error has occurred: java.lan.NullPointerException
In this testing, we can conclude that the Domain Functional Level upgrade from 2000 to 2003. The MI logon will fail.
Q1. Crystal Report XI R2 cannot run on Windows 2003 server (Domain Functional Level: 2003)?
Q2. If Crystal Report XI R2 can run on Domain Functional Leve: 2003, how to fix our problem?
Do you have any idea to help us? Thanks!
Edited by: Initiator on Jul 20, 2010 6:22 AM

Domain Functional Level: 2008 R2 to 2012 R2

My current forest and domain functional levels are 2008 R2. I know I can safely upgrade the functional levels in most cases, but I want to specifically know with regards to Lync.
Our entire environment, including Lync, is running on Windows Server 2012 R2. (We have no domain joined clients.)
Can I safely raise the forest and domain functional levels to 2012 R2 without impacting Lync?

you can easily upgrade the funtional level without any issues since you have all the Domain Controllers on Win server 2008R2.
http://support2.microsoft.com/kb/2869728/en-us
For more details : Listed below link has the table which shows the effects of upgrading the domain functional levels to Windows 2012
http://technet.microsoft.com/en-us/library/understanding-active-directory-functional-levels
pankaj(MCT)

Cannot Replicate after upgrading domain functional level

Hello,
Parent and child domain. Parent domain (forest) still in domain functional level 2003. However, child domain i just updated to domain functional level 2008 R2. Now replication is not working. I believe the issue is dns, but i do not know what could be different
the names have not changed? This is a two way transitive trust between domains.
Frequent messages from dcdiag dns, are
no DNS RPC connectivity (although i have tried restarting dcom, netbios and frs)
Also in event viewer many 13508 errors
Any help is greatly appreciated thank you.

Have you restarted the DCs after that you raised the functional level? The password of the krbtgt account is reset when the DFL is raised from 2003 -> and sometimes the DCs need to be restarted for the authentication to succeed up to the root.
If you from a Windows Server 2008 R2 DC run dcdiag /test:dns /E dose it report any errors?
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Error Domain functional level

Hi i have that error in my Domain Controller. Install Windows
Server 2012 R2, and I want to raise the functional level.
This Domain Controller no longer exists,
but is within the domain.
To update the domain functional level, the Active Directory Domain Controllers in the domain must be running the appropriate version of windows.
domain Name
xxxxxx.local
Current domain functional level
Windows Server 2008
The following Active Directory Domain Controllers are running earlier versions of windows:
domain Name AD DC Version of Windows
xxxxxxx.local server.xxxxxx.local Windows Server® 2008 Standard 6.0 (6001)
that I can
do?

it might be in the "LostAndFoundConfig" container in the Configuration partition.
Something like this should be logged:
Event Type: Warning
Event Source: NTDS General
Event Category: Directory Access
Event ID: 1723
Date: 6/4/2005
Time: 7:39:52 AM
User: NTDEV\A1ADCH
Computer: NTDEV-DC-07
Description:
Active Directory failed to raise the functional level of the domain or forest
because the following domain controller is at a lower functional level.
Object (forest or domain):
DC=ntdev,dc=corp,DC=microsoft,DC=com
NTDS Settings object of domain controller:
CN=NTDS Settings,CN=LostAndFoundConfig,CN=Configuration,DC=ntdev,DC=corp,DC=com
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Delete the 'NTDSA' object from the "LostAndFoundConfig" container using ADSIEdit.
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

AD FS Across Differing Domain Functional Levels

My customer needs to implement AD FS for single sign on due to a cloud based email solution they recently implemented. The problem is, their domain controllers are Server 2003 (non-R2) at a functional level of 2003 mixed mode. They should be able to raise
to 2003 native if necessary however. Their solution is to create a new 2008 domain and implement a two-way trust, running AD FS in the new domain serving the clients in the 2003 domain. This way should be quicker than upgrading their current domain
which would be a rather large project due to their size and complexity.
Are there any gotcha's I should know about with doing it this way? I have verified that we can create the two-way trust between domains of these functional levels, and AD FS can service clients in a trusted domain, but I am not entirely sure if AD
FS will care that the trusted domain is 2003 non-R2. Can anyone confirm if this will be a feasible scenario?
Thanks very much!!
Wraith

Hi
Wraith,
In addition, if you are not using Windows Server 2012 or above as ADFS server, you will be fine with Windows 2003 mixed mode.
“Since ADFS does not require Active Directory functional-level modifications to operate successfully. However, if you are using Windows NT token–based applications and
you want a token to be generated using Kerberos Service-for-User (S4U), the domain functional level must be Windows 2000 native or Windows Server 2003”, quoted form below article:
Appendix A: Reviewing ADFS Requirements
http://technet.microsoft.com/en-us/library/cc778681(v=WS.10).aspx
More information for you:
ADFS and Domain Functional Level
http://social.technet.microsoft.com/Forums/windowsserver/en-US/5cc0e898-eae2-46ce-8491-5ccf61380423/adfs-and-domain-functional-level?forum=winserverDS
ADFS requirements
http://technet.microsoft.com/en-us/library/cc727972(v=WS.10).aspx
Best Regards,
Amy

Lync 2013 credentials problems on domain computers

Hi folks,
We are having trouble with Lync 2013 and credentials on our domain computers. We have been using Office 365 and Outlook for our email for a couple years and it has worked well enough, so recently we decided we wanted to start using Lync as well. We deployed
the Office 365 Pro Plus suite available to us through our Office 365 subscription and signed in. The first sign-in went as expected. It asked for a username and password, asks if it should remember those credentials for next sign-in (yes), then connects and
everything with Lync itself functioned normally. Subsequent sign-ins have not been normal.
When a user restarts their computer and launches Lync it remembers their user name but not their password. Once they type their password in it asks if it should remember those credentials for next sign-in again, then connects. If a user exits and re-launches
Lync without restarting it remembers their credentials and signs in properly, but then immediately a popup box appears saying that "Credentials are required" in order for Lync to get calendar information from Outlook ( http://i.imgur.com/hqcK426.png
We know the problem is only happening with computers on our domain, but we don't know why. I tested things out on my home desktop and network by installing Office 365 Pro Plus, setting up Outlook, and then Lync. Both Outlook and Lync auto-discovered everything
normally after getting my credentials and Lync behaves as expected every time the program launches. I then brought my personal laptop in and tried the same thing on my work network to see if it is network related, but Lync behaves normally on that computer
as well.
I originally worked on the problem at the Office 365 Community Forums ( http://community.office365.com/en-us/f/166/t/246014.aspx ), but after we isolated the problem to something with the domain computes I was told that they could not help me any further
and was referred here. Does anyone have any ideas as to what is keeping Lync from behaving properly on our domain computers? We have a mix of Windows 7 x64 and Windows 8.1 x64 computers, all joined to the same domain and with the same basic suite of software.
Thanks,
~Misharum
PS: How do I verify my account? The outlook.com email address has been verified, but I don't see anywhere to do verification in my TechNet profile here.

Yeah, the clients are fully patched. I put a support ticket in through Office 365 and the rep there was able to help me. It ended up being two separate problems.
Lync was not remembering my credentials to automatically log me in between restarts:
Installed the latest version of the Microsoft Online Services Sign-In Assistant.
After signing signing into Lync another popup appeared asking for credentials again to access calendar information. (two steps to solve this one).
In Active Directory Users and Computers, open up the properties of each affected user, go to the Attribute Editor tab, find and double click the proxyAddress attribute, and add in
sip:[email protected] where the userid is the user's login name and domain.com is your domain. I'd imagine this is scriptable in PowerShell but I don't know enough to do it.
Then on the computer that the users will be using, while the user is logged in, add a dword of NoDomainUser = 1 in the registry at HKCU\Software\Microsoft\Office\15.0\Common\Identity. The most sensible way to do this in my mind is with a group policy so
it will get written to each user's registry under their profile when they log in.
After doing all of this Lync remembered my credentials between restarts, signed me in automatically, and only gave that credentials popup on the first sign-in after applying both changes in step 2.

Lync 2013 and Raising Forest/Domain Functional Level?

Similar Messages

Maybe you are looking for