LOL - oopsie! Sorry Brian and Ben.

From: Michael B. Smith [mailto:[email protected]]
Sent: Monday, October 17, 2011 8:52 AM
To: NT System Admin Issues
Subject: RE: Lync server

I can assure you - Brian looks nothing like Ben.

:)

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: David Lum [mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Monday, October 17, 2011 9:45 AM
To: NT System Admin Issues
Subject: RE: Lync server

Ben you are money. Looks like my ROOTDC and SUBDOMAINDC in my virtual world 
aren't fully communicating. They can ping by IP but not name, so name 
resolution troubleshooting ensues..

From: Brian Desmond 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Friday, October 14, 2011 8:07 PM
To: NT System Admin Issues
Subject: RE: Lync server

Having the schema master in a subdomain is fine. It sounds to me like you have 
a global catalog or trust problem, though. If you login with a user in the root 
domain (in schema admins), is it in your token?

Have you done a metadata cleanup of the missing DCs? If you connect to the 
child domain DC with LDP, is isGlobalCatalogReady==TRUE?

Thanks,
Brian Desmond
[email protected]<mailto:[email protected]>

w - 312.625.1438 | c   - 312.731.3132

From: David Lum [mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Friday, October 14, 2011 9:12 PM
To: NT System Admin Issues
Subject: RE: Lync server

Ok here's something: Checking this out while ROOTDC1 is in the root of the 
forest, the schema master is actually SUBDOMAINDC1 (seems weird). I have VMs of 
ROOTDC1 and SUBDOMAINDC1 but neither od the "DC2" servers.

Roles:
Schema master: SUBDOMAINDC1
Domain naming master: ROOTDC1
RID: ROOTDC1 (for root), SUBDOMAINDC1 for subdomain)
PDC: ROOTDC1 (for root), SUBDOMAINDC1 for subdomain)
Infrastructure: ROOTDC2 (for root), SUBDOMAINDC2 (for subdomain)
GC: ROOTDC1, SUBDOMAINDC1

Where do I look to fix my issue?

Dave

From: David Lum [mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Friday, October 14, 2011 6:57 PM
To: NT System Admin Issues
Subject: RE: Lync server

OK That's firggin' weird, I just learned of whoami as a Win command yesterday.

And doing that...no, I am not! In my sandbox I have cloned 2 of our 4 
production DC's - one is a forest root machine and the other is a subdomain DC. 
Am I possibly missing a critical role master?

Dave

From: Brian Desmond 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Friday, October 14, 2011 5:04 PM
To: NT System Admin Issues
Subject: RE: Lync server

IF you run whoami /groups, is it listed?

Thanks,
Brian Desmond
[email protected]<mailto:[email protected]>

w - 312.625.1438 | c   - 312.731.3132

From: David Lum [mailto:[email protected]]<mailto:[mailto:[email protected]]>
Sent: Friday, October 14, 2011 3:56 PM
To: NT System Admin Issues
Subject: Lync server

I am trying to install a Lync server in a sandbox with some DC's. When I run 
the deployment wizard and try to extend the schema it tells me it can't 
complete the command because I am not in the schema admins group....oohh, but I 
am!

One slight twist is I am using an account from subdomain.nwea.org that is in 
schema admins group in nwea.org, but as that account is in schema admins it 
shouldn't matter.

Anyone run into this? It gives me this message when I run "prepare Active 
Directory for Lync server
http://www.ocspedia.com/fe/Install_Microsoft_Lync_Server_2010.aspx?ArticleID=103
David Lum
Systems Engineer // NWEATM
Office 503.548.5229 // Cell (voice/text) 503.267.9764


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
[email protected]<mailto:[email protected]>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to