I'll be spinning up a new Nextcloud instance and simply manually migrating users to it I think.

@dashrender said in Server 2012 R2 not installing Updates:

@scottalanmiller said in Server 2012 R2 not installing Updates:

@dashrender said in Server 2012 R2 not installing Updates:

Of course though - this thread is about Windows Server, not desktop - where this should be MUCH less of an issue with properly designed code.

Same code, they don't make it twice. Less hardware hotplugging, but probably just as many lines of code in use.

Less desktop apps on the platform, but you're right - the base code is the same.

Fewer desktop apps, maybe. But in the Windows world, server often is treated as a desktop (like 90% of the time) so the reduction is rarely what you'd hope. And there tends to be lots of server-only code too, often running as desktop apps.

So this morning, no one on RDS had printers again.

WTF..

So I manually added a printer direclty on the RDS server (not from the Print Server (the DC)). IT showed up immediately on all users and was able to be printed to.

So I manually added all the printers direct. Issues resolved for the moment.

FFS Microsoft...

So piss off Microsoft.. I so do not want to remove and add a role to resolve a role not working right......

But I found no other solution yet.

Sorted this out.
For some reason the install was setting Allow Global IP and Allow Default Route.
Once I unticked these and ticked All Managed IP it all began working.

@IRJ said in Windows Server 2012 R2 - Share Auditing for Changes:

I know you use wazuh..

Check this out

https://documentation.wazuh.com/current/user-manual/capabilities/file-integrity/index.html

Thanks! Checking out setting this up. Hopefully, it will reveal the culprit.

@ilyas said in Reset 120 Day Grace Period for Windows RDS Server with PowerShell:

@scottalanmiller

Hi, Thanks for wonderful script that save my time.
Could You please guide me how we can run this script on multiple servers?

I tried foreach PowerShell method but it does not work.

From the ISE, load the script and then enter-pssession for each system. Once connected, run the script from the ise. Sorted.

Good find.

Our go-to solution for VSS problems is to set up a dedicated snapshot volume. Otherwise we were getting timeouts and M$ does ugly things that don't make sense when VSS doesn't work properly.

@Obsolesce said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@Obsolesce said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@Obsolesce said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@Obsolesce said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@Obsolesce said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@Obsolesce said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@Obsolesce said in Windows Server 2012 R2 : randomly changes date/time ?:

@WrCombs said in Windows Server 2012 R2 : randomly changes date/time ?:

@DustinB3403 said in Windows Server 2012 R2 : randomly changes date/time ?:

I've seen the time slip, usually caused from a aging bios battery. But where time is jumping all over the place. That's a new one.

after I re synced, It slipped an hour ahead.

Check (as in look at) the timezone and the automatic daylight saving check box

Says eastern time .

wont let me change to Central Standard either

What do you mean it won't let you? Is it grayed out? Is there a link to click in the window to enable changes to be made?

When I change it to CST it says " Your current time zone is not recognized, Please select a valid time zone. "

Try PowerShell:

Set-TimeZone -Name "Central Standard Time"

Or whatever zone you're in and is current.

Powershell blows up

Don't know what that means. Screenshot?

Capture.PNG

even with copy paste it does that
and elevated

What's the result of this:

$PSVersionTable

Capture1.PNG

Oh. That's why. Are you able to install PS v 5.1?

I don't know the CMD.exe way to do it.

Im not sure, Give me a few

I'm sure a reboot would be required somewhere... but if you can, I found this:

https://social.technet.microsoft.com/Forums/ie/en-US/3b13b6a0-ecb2-429d-ad8d-533b7322c7ee/installation-of-powershell-50-on-windows-2012-r2

I did not do this,
I did however set it up to not be accessible from anyone but our Account which is completely locked and no one has the password, to see if the issue goes away.

@JaredBusch said in DNS Update Issue:

@scottalanmiller the issue with nslookup being useless is stupid though.

Agreed, that's really messed up.

@donahue that's more of what we would expect.

Must've been that one server. Seems like it's running fine on another one.

@dbeato said in Error: The flush and hold writes operation on volume timed out while waiting for a release writes command.:

This might be Crashplan not supporting SQL Open files as you can see here:
https://support.code42.com/CrashPlan/4/Backup/Back_up_open_files_and_databases

Yes, we looked around to find some that weren't where they were supposed to be and might have been open. Hoping that that might end up being all that the issue was.

@dbeato said in Windows 10 Hyper-V Manager unable to connect to Server 2012 R2:

@jaredbusch said in Windows 10 Hyper-V Manager unable to connect to Server 2012 R2:

, in an elevated command prompt you run this.
MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.

Interesting, that was the issue you were having last week right?

Nope. Different client.

That location is a firewall issue.

I've had this happen on multiple occasions. The system was configured to use the internal windows database instead of sql, and there were too many records so the refreshes and etc. would take forever, or you'd get the reset server node issue. After I migrated the database to sql, the problem mostly went away. It still occurs on slow connections.

@tim_g said in Replacing a failed CA:

@kelly said in Replacing a failed CA:

@dashrender said in Replacing a failed CA:

@kelly said in Replacing a failed CA:

@tim_g said in Replacing a failed CA:

@kelly In what way is your DC using certificates?

Domain Controller Authorization and Domain Controller.

I ended up just deleting the certs within CertMgr on the DCs themselves, and then requesting new ones. It appears to have fixed the problem.

I was wondering if it would simply be that simple.

I was leery of doing it at first since I didn't know what all was tied to those certs. In the end I just decided to go for it.

You could always export the cert first before deleting it. That way you can always put it back.

Too late for that... cough
0_1510771545875_quote-damn-the-torpedoes-full-speed-ahead-david-g-farragut-342437.jpg

I ended up going with an upgraded script by truly using powershell.

I found the answer here -
https://stackoverflow.com/questions/936108/how-to-script-ftp-upload-and-download

Essentially this is the script:

$File = "D:\Dev\somefilename.zip"
$ftp = "ftp://username:[email protected]/pub/incoming/somefilename.zip"

"ftp url: $ftp"

$webclient = New-Object System.Net.WebClient
$uri = New-Object System.Uri($ftp)

"Uploading $File..."

$webclient.UploadFile($uri, $File)

Loving the Marvin Gaye reference in the title.