Posts made by BRRABill

Well, except for "G" ... WTH?

I had it on all the root hint servers, and also the forwarders.

  The A record for this DC was found
  The SOA record for the Active Directory zone was found
  The Active Directory zone on this DC/DNS server was found
  Root zone on this DC/DNS server was not found

  TEST: Forwarders/Root hints (Forw)
           Recursion is enabled
           Root hint Information:
              Name: a.root-servers.net. IP: 198.41.0.4 [Invalid]
              Name: b.root-servers.net. IP: 192.228.79.201 [Invalid]
              Name: b.root-servers.net. IP: 199.9.14.201 [Invalid]
              Name: c.root-servers.net. IP: 192.33.4.12 [Invalid]
              Name: d.root-servers.net. IP: 199.7.91.13 [Invalid]
              Name: e.root-servers.net. IP: 192.203.230.10 [Invalid]
              Name: f.root-servers.net. IP: 192.5.5.241 [Invalid]
              Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
              Name: h.root-servers.net. IP: 198.97.190.53 [Invalid]
              Name: i.root-servers.net. IP: 192.36.148.17 [Invalid]
              Name: j.root-servers.net. IP: 192.58.128.30 [Invalid]
              Name: k.root-servers.net. IP: 193.0.14.129 [Invalid]
              Name: l.root-servers.net. IP: 199.7.83.42 [Invalid]
              Name: m.root-servers.net. IP: 202.12.27.33 [Invalid]

When you run dcdiag /dns ... do you get errors with the root servers, such as this?

DNS server: 198.41.0.4 (a.root-servers.net.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4
[Error details: 9002 (Type: Win32 - Description: DNS server failure.)]

I think I have found the culprit.

When I added the most recent DC, I demoted another one, named ORCA.(I am a JAWS fan, what can I say?)

In DCDIAG DNS testing, that server is still listed, and as an error. I looked through the AD DNS and noticed it is still in there in multiple places.

Is it safe/proper to delete all orphaned entries/mentions of that?

From DCDIAG:

            DNS server: 10.0.2.1 (orca.domain.com.)
               2 test failures on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 10.0.2.1
               [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
               Delegation is broken for the domain _msdcs.domain.com. on the DNS server 10.0.2.1
               [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.) - Delegation is broken for the domain _msdcs.domain.com. on the DNS server 10.0.2.1]

DCDIAG results...

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\DC04
      Starting test: Connectivity
         ......................... DC04 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\DC04
      Starting test: Replications
         ......................... DC04 passed test Replications
      Starting test: NCSecDesc
         ......................... DC04 passed test NCSecDesc
      Starting test: NetLogons
         ......................... DC04 passed test NetLogons
      Starting test: Advertising
         ......................... DC04 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... DC04 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... DC04 passed test RidManager
      Starting test: MachineAccount
         ......................... DC04 passed test MachineAccount
      Starting test: Services
         ......................... DC04 passed test Services
      Starting test: ObjectsReplicated
         ......................... DC04 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... DC04 passed test frssysvol
      Starting test: frsevent
         ......................... DC04 passed test frsevent
      Starting test: kccevent
         ......................... DC04 passed test kccevent
      Starting test: systemlog
         ......................... DC04 passed test systemlog
      Starting test: VerifyReferences
         ......................... DC04 passed test VerifyReferences

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : brra
      Starting test: CrossRefValidation
         ......................... brra passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... brra passed test CheckSDRefDom

   Running enterprise tests on : brra.com
      Starting test: Intersite
         ......................... brra.com passed test Intersite
      Starting test: FsmoCheck
         ......................... brra.com passed test FsmoCheck

LOL, yeah I don't really have a choice.

Still on "Server 2003"

I know, I know ... working as fast as I can to get all this upgraded.

Literally almost to the point of being able to upgrade to 2016, but had a few road bumps, and now this road bump.

I think I might be having some trouble with my domain.

The other day I rebooted one of my DCs, and it took a while for me to be able to log in. I kept saying that it could not find a domain controller.

Today, I tried joining a clean install Windows 10 machine to the domain, and am getting a

"DNS name does not exist" error
The query was for the SRV record for _ldap._tcp.dc._msdcs.BANDR

No issue logging in or anything, so I tok another WIn10 machine off the domain and tried to add it back in, and got the same error message.

I have the original DC that we've had forever on the network. I added a second DC a while back, the does AD and DNS.

Thoughts on where to start?

Still in favor of tshirts, however.

@jaredbusch said in Dell Perc H710 predicted failure:

@brrabill said in Dell Perc H710 predicted failure:

@jaredbusch said in Dell Perc H710 predicted failure:

Don’t wait don’t delay just fucking do it

You should start making tshirts with this quote

Learn something today from your failure to reboot more did we?

Not really.

Wouldn't have helped. Would have just messed up whatever weekend i did it on.

@jaredbusch said in Dell Perc H710 predicted failure:

Don’t wait don’t delay just fucking do it

You should start making tshirts with this quote

@dustinb3403 said in XenServer Not Booting:

The culprit is likely that you'd didn't point your logs to a different directory, and those logs being written destroyed the USB.

No logs written to USB.

We spent forever going over all that, remember?

RE: XS on USB comments ... trust me, I'll never do it again.

@dustinb3403 said in XenServer Not Booting:

I've had this happen in my lab, and it's always been resolved by reinstalling and the USB drive is usually dead and unable to be used elsewhere.

Yeah, that is what I am wondering.

Was having a few issues with my XenServer this morning. The host itself eventually froze up with this:

So I rebooted it. It took a long time for it to come up, and then it booted into Emergency Mode.

It boots off a 64GB USB stick. The VMs are stored on a 1.8TB SSD array (DELL H710).

Here is the first thing it says in emergency mode:

And here is a listing of the drives and partitions.

Anyone have any thoughts? sbd is a unused partition I am considering reinstalling XS on to see if I can re-see the array. But thought I'd maybe see if it is fixable first.

Though wondering if the USB drive just finally gave up the ghost.

@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:

@wrx7m said in Potential Office365 (Exchange Online) Throttling Issue:

@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:

I like either the Azure method or the MigrationWiz. With the latter you can migrate ahead of time and sync up after the switch or do a dial tone migration if you don’t have the time to plan.

Azure is more work but when migration hundreds of large mailboxes it’s better than the outlook import method.

Soemthing to note, when you migrate a premise exchange server you get full speed upload automatically from MS.

Seems like with the limits raised we complete Terrabytes of mail migrations over a weekend without anyone left behind. I’ll have to pay attention next weekend on what speeds were seeing in live migration.

I was in hybrid mode and it still took a long time.

I did not have that experience, have done it twice.

Maybe they are throttling it more.

My next step with be the IMAP product you mentioned. We'll see where we get with that.

@wrx7m said in Potential Office365 (Exchange Online) Throttling Issue:

They are throttling. I just went through a 100 mailbox migration and a user with a 15 GB mailbox took 3 days. I have a 150/150 Mbps dedicated fiber circuit.

Yeah this is basically what I am saying.

Plus these "higher speeds" they discuss are with concurrent users.

So that could be why. If you happen to have 100 users and they are all 5GB mailboxes you will complete over a weekend.

You have 100 users with 20GB mailboxes, you are in for a world of hurt.

@dbeato said

https://support.office.com/en-us/article/what-you-need-to-know-about-migrating-your-imap-mailboxes-to-office-365-3fe19996-29bc-4879-aab9-5a622b2f1481

@bigbear said that is a disaster, and that's about the feel I got from it from reading stories online, as well.

We can argue the point all we want, but the thing is, there IS an easy way to do this. It's just the Microsoft cripples it for some reason.

@dbeato said

I am not sure from what email system you are coming from

IMAP

@dbeato said in Potential Office365 (Exchange Online) Throttling Issue:

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

Trying the PST import method. Honestly, it isn't much better.

Have a 3.28 GB PST upload to Office365 already. Started the import at 2:03. It is now 6 hours later and it is only 59% done. So this seems like it might even be SLOWER than the other way.

WTH, Microsoft. Why do you make it so hard to switch to your product?

I am still amazed at how long it has taken you, I am not sure from what email system you are coming from but usually I do importa initially a month or 2 weeks before and then do deltas every week with the Builtin migration tool.

I guess my mistake is expecting it to happen it like every other file transfer would happen.

I mean, the upload of the PST to Azure went almost full ISP speed of 65 Mbps. Why the F do they import the data at .5GB an hour or less. Just makes no sense why they would want such a delay in allowing people to switch over to their system.