We find that if we rename the PC, then allow more than a day to go by before restarting, this can happen.

Also, if we rename a PC, then the user allows the PC to go into Lock mode (screen saver timeout with login required to return) they will encounter this upon wake up/re-logon.

In the above two cases a reboot usually resolves it, when it doesn't, we go in as local admin and disjoin then rejoin the domain to resolve it.

Also, in the above two cases, we did not lose the computer in active directory, so after the disjoin/rejoin you'd want to remove the orphan computer from AD.

There's an article online somewhere about why you should NOT disjoin and rejoin the domain in this case, but we have always done it this way and have never experienced ill effects.

@black3dynamite said in Roaming Profiles killing local copy:

@Dashrender said in Roaming Profiles killing local copy:

@travisdh1 said in Roaming Profiles killing local copy:

@flaxking said in Roaming Profiles killing local copy:

Just wondering if any of you with more experience with Roaming Profiles can explain this behaviour.

There's an old Roaming Profiles set-up that's been dragged along through the years and we're wanting to senset it.

One thing we're seeing is that for users who's roaming Profiles write-back haven't been working, (maybe permission error on some files) if we do something that might trigger it to star working again (like add folder exclusion), their local profile gets nuked.

It seems like this is only an issue with roaming Profiles that haven't been working, if they've been working, any changes we've made hadn't had the affect off killing the local profile and starting fresh.

I've check for any GPO settings that might be asking for the local profile to be deleted, but I haven't found anything. From what I understand, the profiles should only be merging.

Has anyone else seen behaviour like this before where a roaming profile goes from not working to working and it kills the local copy?

It's been a long, long time since I touched anything with roaming profiles. Just about everyone uses redirected folders now if they need that sort of functionality, and this is one of the reasons. Roaming profiles just proved very buggy historically.

man, I dislike redirecting things like the desktop... it's no longer a local folder and makes using it as a scratch pad super slow...

Ever since I embraced using OneDrive and Nextcloud, I would use junctions points. Folders like Desktop, Documents and so on would be stored in the OneDrive or Nextcloud folder and then I would use junction points. The user shell folders paths will still stay the same.

This is what I do.

@scottalanmiller said in MS SQL Server 2016 on Windows Server 2019?:

Trust me, we tried to go Linux. But it just didn't work out.

OH NOES!

@black3dynamite said in Windows Server 2019 Need to Download and Run without AV Deleting Files:

https://www.thomasmaurer.ch/2016/07/how-to-disable-and-configure-windows-defender-on-windows-server-2016-using-powershell/

For now, just temporary disable Real-Time Protection via PowerShell
Set-MpPreference -DisableRealtimeMonitoring $true

Download the executable and scan it manually before you install
Start-MpScan -ScanPath C:\datastore\file.exe -ScanType QuickScan

Enable Real-Time Protection after the install
Set-MpPreference -DisableRealtimeMonitoring $false

Excellent, now THAT did it.

@scottalanmiller said in Windows Server 2019 Basic Installation:

@dbeato said in Windows Server 2019 Basic Installation:

@Obsolesce said in Windows Server 2019 Basic Installation:

@scottalanmiller said in Windows Server 2019 Basic Installation:

@Obsolesce said in Windows Server 2019 Basic Installation:

@scottalanmiller said in Windows Server 2019 Basic Installation:

@JaredBusch said in Windows Server 2019 Basic Installation:

The current install method brings Windows Server on parity with the Linux ecosystem really. You install, choose some options and end up at a prompt after reboot. Then you remotely add the features and shit you want.

Yeah, very in like with Fedora, Ubuntu, or Deepin. Deepin might still be my favourite installer for normal stuff of the four.

Did you have a Deepin install screenshot chain on here?

No, but I do it so often, it would be easy to get.

That'd be nice to see on here.

Last post on it was below
https://mangolassi.it/topic/14453/deepin-linux-15-4-1-install

The install still looks like that.

LOL that's not an installer. That's a push button, get peanuts.

Nice though.

@EddieJennings said in Windows Server 2019 Updates:

I'm create a template VM for Server 2019 (one with and one without the GUI). I'm curious to see if any of you have seen the following behaviors.

Non-GUI

Use sconfig to download and install updates. Choose All updates, download, and install. After notification the updates were installed (appears about 5 seconds after choosing to install), you're prompted to reboot. After reboot, check for updates again to find the same updates still listed, repeat from step 2 endlessly.

GUI
Updates stay forever at "pending dowload"

GUI and using sconfig
Same behavior as using sconfig in the non-GUI environment.

Nope, you got something weird going on.

@Reid-Cooper said in General Guidance on Windows Admin Center WAC:

@Obsolesce said in General Guidance on Windows Admin Center WAC:

Yes you do need to either add other devices manually or by importing a list... but it's a one-time thing so it's a non-issue IMHO.

Not bad for tiny environments. But at any scale, how does that handle machines being added in the future? You have to manually add every new machine after every change to WAC?

I've only had about 100 servers and a handful of Win10 in it, so I'm not familiar with handling that at scale. It really only requires a txt file of a list of devices which is simple to maintain in any aspect. I only had to import that to get everything back in. If I added a new server, I would add it to the text file then add that server.

@Emad-R said in Download Windows Server 2019:

@scottalanmiller

https://software-download.microsoft.com/download/sg/17763.253.190108-0006.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso

Thanks @Emad-R with this link you don't have to go through all the paperwork.

@PhlipElder said in Windows Server 2016 or 2019:

@NashBrydges said in Windows Server 2016 or 2019:

Setting up a new server and new VM for a client and need to buy a new Windows Server license. I would usually go to the most recent but wondering if anyone here has had any experience that would suggest sticking with a previous version instead? The VM will host an application that only runs on Windows so any mention of Linux isn't an option.

We've been running Windows Server 2019 since GA with nary an issue. There are a lot of under the hood improvements in 2019 so I suggest running with it.

No different than any other large OS dev cycle. Look at 2003, 2003 R2, 2008, 2008 R2, 2012, 2012 R2, 2016, 2019. Roughly equal leaps between them all. It's almost never about features, it is 2-4 years of additional fixes, research, improvements, advances, clean up, etc. Features do play a part, but the lesser part.

You only lose on the core licensing if you have more than 16 cores on two processors or you have 1 processor wiht less than 16 cores.

1 processor with 16 cores = 1 16 core server license
1 processor with 12 cores = 1 16 core server license
1 processor with 8 cores = 1 16 core server license
2 processors with 8 cores = 1 16 core server license
2 processors with 12 cores = 1 16 core server license + 4 2 core server license packs

Microsoft designed it around the most common system being sold. Intel Xeon dual proc 8 core systems.

@black3dynamite said in Windows Server 2019 Goes Into Preview:

When will we see the availability of Hyper-V Server 2019?

Preview is already out, I believe.