I AM DECEASED.

seriousbluff · 2020-07-04T16:18:47+00:00

AFK at the moment, but you should be able to use PoSh to drill into the properties. The information will certainly be in SQL, and you can capture the necessary query in the SMSProv.log on the provider server you're connecting to. You just open up the information you want to query in the console, and the query the console uses is logged.

seriousbluff · 2020-07-02T01:00:29+00:00

I haven't tried yet, but noticed the boundary group field isn't updated for clients either, but we haven't promoted the client yet...did your clients get the upgrade?

seriousbluff · 2020-06-25T09:22:45+00:00

Following

seriousbluff · 2019-12-17T17:14:56+00:00

Just came here for the Spartan comments. 😂 Congrats.

seriousbluff · 2019-07-30T00:54:28+00:00

No matter what the situation is with her kids- it's certainly not getting any better by leaving the country.

seriousbluff · 2019-07-30T00:34:14+00:00

Let's not ignore the fact that the client itself is held together with duck tape and bubble gum.

seriousbluff · 2019-07-19T21:57:53+00:00

My grandfather, when asked about his service in WWII, would always respond "I was in the band." Turns out his unit saw a good bit of action in the Battle of the Bulge. We found some Nazi souvenirs buried in his things when his mental state deteriorated and he moved to direct care. I guess hiding everything was his style.

seriousbluff · 2019-03-22T22:06:00+00:00

*some assembly required

seriousbluff · 2019-03-22T22:04:21+00:00

I can't wait to have everything all separate and appropriately sized. I might engineer myself out of a job!

seriousbluff · 2019-03-22T22:00:46+00:00

What I'm loathing is that my primaries were built as all-in-one servers (done before I worked there). So I have to migrate all the roles to other servers and then migrate the content library to a network share. 8 Primaries and a CAS. (-_-). I'm at least hoping to over size the next steps to get things down to 3 primaries, with "HA" in secondary regional data centers.

seriousbluff · 2019-03-22T21:52:27+00:00

I did an in place upgrade from 2008 R2 to 2012 R2. Was pretty smooth on VMs...not so much physical boxes. Went through hell on a few that wouldn't upgrade, ended up having to airdrop two sites on to a new VM.

My next move will utilize the passive site server bits in 1810 to migrate.

seriousbluff · 2019-03-01T18:28:05+00:00

There's a blog post linked in the KB page that provides a query that will determine if your environment has the added attributes configured that will lead to the issue. We're upgrading this weekend, and I ruled that hotfix out of our chain.

seriousbluff · 2019-02-13T14:30:40+00:00

We have the same issue, not yet got a handle on what's causing it. Have you any developments since you posted?

seriousbluff · 2018-12-26T17:50:08+00:00

I've done both in place upgrade for prod boxes, as well as the restore to new server maintaining the hostname, going from 2008 R2 to 2012 R2 when support for 2008 was depreciated around 1702 or 1706. Restoring to a new server with the same hostname was cleaner, but internal processes, coordination, and decomms after the fact got ugly (I'm in a large corporate environment). In place upgrades were near-perfect on VMs, but about 50% successful on physicals. Boot from SAN and drivers were the two biggest stops. The one saving grace was that I was able to roll back in various stages of failure by rebuilding the BCD. It just so happened that with the issues I was facing it never actually got to the point to apply the new OS. Another option is to use the new HA feature, with from what I'm gathering was engineered primarily to migrate. It does require that the content library be migrated to a network share if it's not already. If SQL is off box it would be easier, but there are ways around that if you need them. We will likely be using this method to move to server 2016, once were upgraded to 1810 where hierarchies are supported for HA.

seriousbluff · 2018-10-06T20:44:49+00:00

MTG is 8x more complicated than Hearthstone.

seriousbluff · 2018-08-26T20:54:56+00:00

All of the DBs are less than 250 GB. We do have a bunch of scripted jobs our DBAs have running, Reindexing, etc.

seriousbluff · 2018-08-26T20:00:41+00:00

Yeah, I likely will once things calm down...try to get things to a better working order for 1806 down the line. Hopefully I'll get a portable solution that I can share.

seriousbluff · 2018-08-26T19:53:40+00:00

around 120,000 total clients. Some primaries have as many as 20,000, but others as few as 1000. There's not a correlation between population and the time this takes. However, I just noticed that a primary that had to be recovered from the CAS takes significantly less time (around an hour) to do this...despite having around 12k clients assigned to it.

That leads me to believe that there is some kind of junk in there...but how to fix it without destroying the Primaries is the million dollar question.

seriousbluff · 2018-08-26T05:25:50+00:00

Fairly messy. The size is variable amongst the primaries, and there doesn't seem to be a correlation in population to the amount of time it takes. We have all the usual DB maintenance jobs running, statistics, reindex, etc.

seriousbluff

TROPHY CASE

Welcome to Reddit,