Server 2008R2

In PowerShell versions less than v5 you'll notice that the friendly Write-Information cmdlet doesn't exist. That's fine, until you write a PowerShell script that uses Write-Information (or any other command that doesn't exist).

Well, this was an annoying issue. I pushed out TCP/IP printers using group policy and pointed them to printers on a print server to pull the drivers and settings. This worked awesome, except for the 45 seconds per printer overhead. I narrowed it down to the universal print driver, by changing the drivers to Generic Text Only. I was going to use the print drivers that came with windows, except for the wonderful problem of the issues between 32bit, 64bit, Windows 7 and XP driver names. If you look

We've run into a problem where some domains would stop resolving from Windows DNS. They would work fine for about a week, then they would stop. I couldn't find anything on the internet, and MS's support people had me try changing the CacheLocking stuff (disable it) by running dnscmd /config /cachelockingpercent 0 then restarting the DNS server. That will disable the cachelocking. Cache locking is basically saying, don't overwrite the cache until the percent of the ttl has expired. Even if it

Alright, here was my problem. I have a 2008r2 file server, tons of files, and we are removing everyone's full access rights and doing 3 groups for each root folder, a full control, modify and read only. We ran into a problem where if you put a user in one of the groups to give them access, they still would not have access. The fix, sort of simple, but dumb. For us, a simple log off and log on of the user didn't fix it. We had to go in after they tried, using computer management, close their conn

There was an event log error entry every time I tried in the Application event log. It was: Faulting application name: TrustedInstaller.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc4b0 Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc00000fd Fault offset: 0x00000000000529f0 Faulting process id: 0x9a0 Faulting application start time: 0x01cb52a9177986b4 Faulting application path: C:\Windows\servicing\TrustedInstaller.exe Faulting modul

We are using DFS-R on our servers to replicate DNN content between multiple servers. It works really well, except for some of our system create PDF documents with the temporary file attribute set. Turns out that DFS will not replicate files with the Temporary file attribute. Lame. I created a simple PowerShell script that will recurse through everything in the sub folders and if it's the attribute is set, it will remove it. Because the attribute changes, it causes the file to sync between the 2