Archive for the ‘Windows Server 2008’ Category
Posted by jpluimers on 2018/06/29
If you get the below error, then your RDP target server needs to be patched.
You can choose to stay vulnerable and modify your policy or registry settings as explained in the first linked article below: that is a temporary “workaround” which I do not recommend. Please update your RDP target servers in stead.
English:
[Window Title]
Remote Desktop Connection
[Content]
An authentication error has occurred.
The function requested is not supported
Remote computer: rdp.example.org
This could be due to CredSSP-encryption Oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660
[OK]
Read the rest of this entry »
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »
Posted by jpluimers on 2018/06/25
Posted in Microsoft Surface on Windows 7, Power User, Windows, Windows 10, Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2018/03/16
From a note a very long time ago: [WayBack] 0x8024400E error with WSUS SP2
TL;DR:
- ensure you have at least KB2938066 installed.
- while upgrading WSUS, ensure you reboot the server after each update.
Related: [WayBack] windows – WSUS clients failing to get updates with error 80072EE2 – Server Fault
–jeroen
Posted in Power User, Windows, Windows Server 2008, Windows Server 2008 R2 | Leave a Comment »
Posted by jpluimers on 2018/02/26
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »
Posted by jpluimers on 2018/02/21
Searching for shutdown isn’t enough as frequent WAS messages also contain that search string.
Searching for shutdown of will work as they match both these:
The process C:\Windows\system32\shutdown.exe (COMPUTERNAME) has initiated the shutdown of computer COMPUTERNAME on behalf of user COUNTERS\Administrator for the following reason: No title for this reason could be found
Reason Code: 0x800000ff
Shutdown Type: shutdown
Comment:
and
The reason supplied by user DOMAIN\Username for the last unexpected shutdown of this computer is: Other (Unplanned)
Reason Code: 0xa000000
Problem ID: ######
Bugcheck String:
Comment: VM host failure
–jeroen
Posted in Power User, Windows, Windows Server 2008 | Leave a Comment »
Posted by jpluimers on 2018/02/19
You might think the Console.log belongs Console.exe. That’s right, but that’s a different thing than the Windows Command prompt that many people call console, but is in fact C:\Windows\System32\cmd.exe on a default Windows installation.
C:\Program Files\Windows Small Business Server\Logs>dir console.log
It belongs to the SBS 2008 console which you can access using the https://sbs2008serverIP/remote (for more details, read [WayBack] Accessing Windows SBS Console) and is served by:
C:\Program Files\Windows Small Business Server\Bin\console.exe
It is started when any user logs on (which is sort of odd) and never log-rotates the log file but keeps the log file locked when the process executes.
So the only way to get rid of a really big console.log file is this:
- Terminate console.exe in the Task Scheduler (
taskschd.msc)
- Move away the old
C:\Program Files\Windows Small Business Server\Logs>dir console.log file
- Start console.exe in the Task Scheduler or logoff/logon
Further reading:
–jeroen
Read the rest of this entry »
Posted in Power User, Windows, Windows Server 2008 | Leave a Comment »
Posted by jpluimers on 2018/02/19
When cleaning out an old SBS 2008 Servers, I saw a huge “DataServiceComponents.log” file. [WayBack] SBS 2008 disk space and the DataServiceComponents.log file – Oxford SBS Guy indicated how to clean it up and pointed to [WayBack] Recovering Disk Space on the C: Drive in Small Business Server 2008 | The Windows Server Essentials and Small Business Server Blog.
Both posts have the problem that many backslashes missing in the the various paths.
So this is how I cleaned the DataServiceComponents.log file using an UAC command prompt:
C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs
net stop DataCollectorSvc
"C:\Program Files\7-Zip\7z.exe" a -t7z -m0=lzma2 -mx=9 -aoa -mfb=64 -md=32m -ms=on -sdel DataServiceComponents-backup.7z DataServiceComponents.log
net start DataCollectorSvc
Note that DataCollectorSvc is the shorthand for the Windows SBS Manager service.
–jeroen
Posted in Power User, Windows, Windows Server 2008 | Leave a Comment »
Posted by jpluimers on 2018/02/02
Here’s how you can find out when your domain password will expire.
net user %USERNAME% /domain
It figures this out for the current logon domain (so it doesn’t work cross-domain) but it is a great help, especially when filtering out just the password information:
net user %USERNAME% /domain | findstr "Password"
This can be done in a more complex way with dsquery or adinfo that are tools to query
Read the rest of this entry »
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2017/12/29
For shrinking VM disk images, it’s important to consolidate NTFS free space towards the end of the this.
I’ve tried many tools, starting with defrag C: /X (which tries, but doesn’t give good results) and found out these steps give the best results:
- Perform an Ultradefrag full optimisation,
- Perform a MyDefrag
Consolidate free space script on the drive.
If shrinking still fails then:
- Try the Ultradefrag at boot time
- Note you have to install the normal version, as you cannot enable boot time defragmentation from the portable version:
- Verify what kind of file(s) prevent shrinking: they show up in red after the MyDefrag session:
- Zoom in them (they can initially as small as 1 red pixel) by clicking on or near them, repeating the zoom long enough so you can hover over with the mouse and the lower part of the screen shows a filename like
where you cannot find much information about “$badclus:$bad:$data” but appear to be clusters marked as bad on NTFS level using something like chkdsk /B.
- If it was a bad sector like above, then try to resolve it with [WayBack]
ntfsfix which ships with GParted live boot:
- boot a [WayBack] GParted — Live CD/USB/PXE/HD drive,
- run GParted to see the drive path (for instance /dev/sda1)
- start a terminal
- run this command:
ntfsfix -b /dev/sda1
which will give output like this:
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
Going to un-mark the bad clusters ($BadClus)... OK
NTFS partition /dev/sda1 was processed successfully.
- boot back into Windows
- on an administrative command prompt run this for the affected drive letter:
chkdsk D: /B
(reboot if needed)
- Shrink the drive using
diskmgmt.msc
If you still cannot shrink, then try [WayBack] http://ftp.raxco.com/pub/download/pd14.0/pd14.0_pro.exe PerfectDisk by Raxco free trial.
Note:
MyDefrag (formerly named JkDefrag) is not maintained any more but the 4.3.1 version in the WayBack machine still works very well as the underlying defragmentation APIs in Windows haven’t changed.
References:
For FAT32:
For GParted / ntfsfix:
PerfectDisk via:
–jeroen
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Vista | Leave a Comment »
Posted by jpluimers on 2017/12/11
schtasks /End [/S <system> [/U <username> [/P [<password>]]]] /TN taskname
[WayBack] End a Running Task
Every now and then you have those Scheduled Tasks consisting of batch files that – despite trying – still ask for user input.
If – even after a reasonable time out – the Task Scheduler still hasn’t killed them, you can kill them by hand with the above schtasks in a snap.
–jeroen
Posted in Console (command prompt window), Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »
The Wiert Corner - irregular stream of stuff 