HPlum78

I will reiterate unless you have something else running on that DC that you can absolutely not do without, then you are best off just killing it and standing up a new one.

Is it not that their IT staff have all transfered to the logistics department as lorry drivers make a truck load more money than the IT boys! Wanted to use packet load more.....

What is the OS on your DC? if your 2016 and above its not that much of a faff. Rendom and gpfixup commands add your new domain name to your Azure AD tenant and set it as primary. There are a few steps that I may have missed but I reckon that about covers it....

Nah not having it, you need to go to Gibbs and Dandy and ask for a new bubble for your level mate.

So those files in the chunck store even if they was created in 2015 when the server was built/ deduplication was configured are more than likely still required as they will have reparse pints associated with them. If that makes sense....

Due to being busy this has moved on a bit and we have gone past my next command of Get-DedupStatus.. I will add my thoughts around deduplication and compression. Deduplication works at the bock level and the algorithm is not concerned about the name of the files. It is looking for matching blocks in its data set, once found these blocks are removed and replaced with a reparse point to the required block stored in the deduplication chunk store. This is a post write process, for reads there is a storage filter driver that repoints read operations to the chunck store when and if a reparse point is hit. Compression on the other hand is done at the binary level in a block, the algorithm eliminates redundant data and when decompression is required that same algorithm is used to rebuild the binary data. This can be done at a volume level in windows or by using your favourite compression utility. Using compression and deduplication on an NTFS volume will mash your data because of the way the post processing of the data happenes and how the CRC is calculated when using volume compression. That said in ReFS drives on Windows 2019 and later now support the use of both deduplication and compression (could be 2016 though just cannot remember) So to answer the question deduplication saves space by removing duplicate blocks of data and storing those in a central location to be rebuilt at read time. Compression removes redundant binary data and uses an algorithm to decompress and rebuild the data at read time.

Run the following: vssadmin list shadowstorage Post back the out please..

There used to be an issue with MFA that would freeze powershell but I thought that had been resolved now....

Tbh @chaplic is bang on, if you do indeed use cloudy based services. If not maybe now is the time....

A couple of writable DCs at your main site and the RODC in the satellite sites that take care of those subsets of users/ computers. Do not see the need to have full blown DCs at satellite sites unless you are going to identify one of those as a DR site then that may change your strategy some what. If site loss is a risk you are going to actively mitigate against then you will have a star configuration for your links If not write the risk up and get your SLT to sign it off. It's swings and roundabouts as either way comes with a host of positives and negatives. Risk assessment is key to the decision making then the cost of mitigating those risks.

What you mean like they are doing right now! for a group of IT professionals we sure like clining on to past... it needs to be seen how good the technology that underpins all this turns out and let's face facts MS is testing this right now with an extended set of beta testers beyond their own staff. It a brave new world out there!

These kinds of things always interest me as it shines a light on risk and how different people perseve risk. So the issue with a password is that with the right amount of GPUs and rainbow tables passwords can be cracked if they are "weak". Even if they are not weak brute force attacks against an institution can be a pain for its users and IT Department to say the least. So MFA is put in the mix to make sure that if an individual/ group of nefarious actors do brute force/ fish a password there is a good chance of them needing the other factor (I say good chance as this is not a guarantee). This is the broad brush stokes around passwords and MFA. So there has been a push towards passwordless, MS have not removed MFA here they have just removed the requirement for a password as a factor to be clear. So it interests me that we turn to the position around if the phone (insert token here) is stolen, this is a big leap in my mind as this now means that those upto yet anonymous nefarious actors are going to step up and turn in to groups willing to go out and steal those from your users! Don't get me wrong there will be cases when a phone (token) gets stolen/ lost and by some coincidence the requirement for another factor is not required but that seems far less likely than what is happening right now with passwords. I will also add that I do not for one second think that thugs are going to start robbing people in the street for their phones/ fingers and eyeballs they will clearly turn their attention to the technology and we will have to see what becomes of those efforts.

Just out of interest you have run the troubleshooting tool? https://docs.microsoft.com/en-gb/azure/active-directory/hybrid/tshoot-connect-objectsync

Sorry I reread the thread with my glasses on...so the objects are in the on prem connector space and synced to the metaverse from what I can tell from the OP

Punishment

Brake....

Long..

monotonous

@paulkerton yep could not agree more one source of truth and all that, but if your homework/ grades (insert another) comes from a separate system/ process then you have to be able to write those details against the single source (if that source can accept the data) these types of integrations are required all over the place in our world. The reason for my question is the cloudy version of broehas an api I guess as I dont have access to the details of the api that its RESTful so we should be able to get a token and post back the info with some kind of script/ powerapp or such likes.

Are you using the cloud hosted version?

Never mind that Exchange 13 is in extended support the supported OS (2012) went extended support this july from memory! So add that to the list of reasons not to do this... Oh and then net framework the list continues. @elsiegee40 is right Its just not smart no matter how much you love something (hell 1/2 of us on here would still be running DOS if it where about the love of it!) @Norphy is also bang on with ADFS again spend the faff getting federated access done via cloud based offering that and your mail service. As one great man said "well that will just about cover the flbys"

I always add this when i see -filter * and - properties * on any command. Can we be careful when running commands with this as you would not be popular running that against large directories! Look back through my pasts posts for more.

https://devblogs.microsoft.com/scripting/restore-ntfs-security-permissions-by-using-powershell/ In Ed Wilson we trust That is on the back of the money used by anyone who has done any scripting in the last 20 years.

So just had a quick look at the sophos API specs, says it outputs as JSON so put the output into a var and then pipe the var into convertfrom-json then you will be able to do var.date and such likes. Essentially formatting the var as structured JSON.

When you make the call to the API, the API returns a string that contains that date? I dont know the API but can you not output that as json? If so it would make using the output so much easier...