Here comes the other part of our work, which is to take these 10,000 customers or a big chunk of them who have bought the vision of a private cloud on-prem and working with them to enable them to deploy it and operate it successfully on their infrastructure and on-prem,”
What kind of fever-dream is this?
I wonder if there’s a way you can blacklist their certificate? I’m not sure if that’ll override the CA trust but it might subvert the updating process
Thanks for that - I hadn’t thought about the rest of the domain in the name.
I was purely thinking about it from a hypothetical risk-mitigation perspective.
As you can imagine, keeping ‘the old crap around’ in case of a need to roll back would be handy in some migrations… Assuming the same IP complicates that.
However, I guess a machine can have multiple IPs so it needn’t be too much of a drama if it’s just a matter of moving the original IP when rolling back…
You are a saint with that kind of compassionate thinking - well done!
did you mean tist?
What a stupid thing to do… Already working elsewhere, probably wasn’t worth the tantrum
Surely they sniffed and stole a bunch before wiping? Might not have been viable, but I can hope!
Crazy levels of work required…
If you expand the applications and services part, you can drill down to a group policy specific log which is awfully verbose.
Another thing it might relate to is if the DC that the client is talking to is busy (this is a long shot, though!).
Once you find the pattern of gpo refresh taking ages and start to map that out (chuck the various phases into a spreadsheet, it’s complicated, you’re looking for scripts processing took a bazillion seconds - but it could be registry or any of the other components) across a few PCs, you’ll be able to validate whether its a single DC
Was it recent (and can you get the credit card agency to revert it?)
So does that mean one needs to run NTP as well as the domain-based time sync, for when the donation based one fails?
Seems weird. I wonder why they’re so cagey about it
That and the gazillion edgewebview processes
That does explain it.
I don’t like it, but it does the behaviour, for sure
(thinking about the dual-communities) I guess that’s part of the growing pains we’re seeing and will probably endure for some time.
I’m all about merging however, but perhaps the community culture needs time to develop (or does that just make it harder to merge?). I gather the .ml instance was less windows inclined and rather happy to see that left behind in /r/… Can’t blame them, but that’s squarely where I sit, unfortunately :)
I vote that both are terrible solutions in the wrong situations (as already indicated by the others).
The hard part is getting people to use them properly!
If ‘the business’ has some ownership of their data and its mostly officey-crap, SP is probably fine and it’s easier for them to see that it’s secured and take some ownership of it. Chances are though that lots of the business units has little dips into each others data on the fringes…
(I’m just burned by a multi-TB file share a whole hospital uses where no one owns any of it and it’s a tangled Gordian knot. Goes back decades, sitting on a SAN that doesn’t give much visibility, just de-dupe)