Windows

Stop de ADDS Service ntdsutil activate instance ntds files compact to c: copy "c:ntds.dit" "c:WindowsNTDSntds.dit" del c:WindowsNTDS*.log Start de ADDS Service

I have heard that lots off people are missing the startmenu in Windows 8. I don’t miss it because I normally use the “Run” to enter my command/application and I have pinned my mosy used apps in the taskbar. What I do recommend to my customers is to start using Windows+X. In Windows 7 this would open the Mobility center, but in Windows 8 this opens a smal menu in the bottom left corner: This provides a lot of options for the most. But if you still miss the startmenu and don’t like the new one, I would recommend Classic Shell (http://www.classicshell.net/). This installs a startmenu that you could customize after your needs. If you like the Windows XP look, then just change to that skin. All settings are stored per user in the registry under HKCUSoftwareIvoSoftClassicStartMenu This is a screenshot of my startmenu with Windows 8 look. Notice that is has two folders, one for the Windows 8 apps and one for the classic apps:

NTFS Permissions for Roaming Profile Parent Folder User Account : Minimum Permissions Required Creator Owner : Full Control, Subfolders and Files Only Administrator : Full Control (Microsoft actually recommends none but it simplifies things if you give admins full control) Security group of users needing to put data on share : List Folder/Read Data, Create Folders/Append Data - This Folder Only Everyone : No permissions Local System : Full Control, This Folder, Subfolders and Files Share level (SMB) Permissions for Roaming Profile Share User Account : Minimum Permissions Required Everyone : No permissions Security group of users needing to put data on share : Full Control

hello smtp.server.nl mail from:<test@domain.nl> rcpt to:<to@domain.nl> data subject: This is a test mail to: to@domain.nl This is the text of my test mail. . quit

Good qual­ity icons and images, espe­cially ones with an alpha trans­par­ency can be time con­sum­ing to make, and are often also hard to find. One source of lots of high qual­ity icons in a range of sizes is Win­dows. Win­dows 7 includes lots of icons which can be use­ful as the major­ity are avail­able in sizes from 16×16 up to 256×256, and come with alpha trans­par­ency. You may have noticed that we use some on our down­loads page — they’re handy to quickly indic­ate file type. Win­dows stores most of its icons inside exe and dll files which makes them inac­cess­ible to stand­ard image manip­u­la­tion applic­a­tions like Pho­toshop. How­ever, once they have been loc­ated they can eas­ily be extrac­ted with the free­ware util­ity IcoFX. Track­ing some of them down seems to be the trick­ier part. Below is a quick ref­er­ence for the loc­a­tions of many of the icons avail­able on Win­dows 7. I will peri­od­ic­ally add more details and any extra icon lib­rar­ies I dis­cover to this list.

List of Control Panel Commands in Windows 8, 7, Vista, and XP Sometimes it’s easier, or maybe even necessary, to open a Control Panel applet from a command line in Windows. Each Control Panel applet can be opened by executing a command, you just have to know what that command is. Control Panel itself can be accessed by executing control from a command line in Windows 8, Windows 7, Windows Vsta, and Windows XP. If you want a way to start a Control Panel applet from a script or from the Command Prompt, the following list of commands for Control Panel applets should help: Note: See my List of Control Panel Applets in Windows for Control Panel applet descriptions and information about changes in applets between the Windows operating systems.

There is a very well known “trick” to hide shares with Windows and that is to put a $ sign at the end of the share name. The problem is that this doesn’t work if you are using DFS Namespaces (DFSN). The reason why it doesn’t work is because DFSN doesn’t advertise shares – it advertises folders and there is an underlying mechanism to transparently redirect computers trying to connect to those folders to the underpinning shares. So if you have folders in your DFS Namespace that you want to hide just as if they were a share, how do you do it? The answer lies in the fact that they are, indeed, folders. Go to the DFSN root server and open up the folder for your namespace. Right-click on the folder you want to hide and choose Properties. Then select the Hidden attribute and click OK. You will be asked if you want to apply the change to this folder only or to this folder, subfolders and files. You only need to apply the change to this folder only. Be mindful of the fact, though, that this trick of hiding the folders only works so long as users aren’t showing hidden files and folders on their computers. If they are, these folders will still show up. To make it even harder for users to find these “hidden” folders, it is necessary to set the System attribute on the folder. This then prevents the folders from being seen unless the user has unticked “Hide protected operating system files”. Setting the system attribute on a folder requires the use of the attrib command with a very specific sequence of flags: attrib –r +h +s <folder path> The –r flag removes the read-only setting which is normally used by Windows on folders as an indicator that the folder might have customisation on it. Since we are talking about folders in the DFS Namespace, that isn’t going to apply here. The +h flag applies the hidden setting. You need to do this as part of the same command as +s in order to make sure that the folder does actually get hidden and not just set as a system folder. You cannot apply the hidden flag after the folder has got the system flag set. The +s flag applies the system setting. Bron

How to place FSMO and Global Catalog roles in Active Directory During installation of Active Directory on a Windows Server 2000/2003/2008 all FSMO roles will automatically be installed on the first server. But Best Practice dictates to move some of theese Flexible Single Master of Operation (FSMO) roles to seperate servers. If you only have one domain controller (not recommended), there is nothing to do since all roles must be on this server, but if you have multiple servers you should move some of theese roles on to more servers. It is also important to be aware of what servers are Global Catalog servers, especially if you have more than one domain and even if only one domain, they will be prefered by applications like Exchange server. It is recommended to place the forest roles on one Domain Controller (DC) and the domain roles on another server. If not all Domain Controllers are Global Catalog servers, it is also important to place the infrastructure master on a server that is NOT a Global Catalog server. Recommended Best Practice setup of FSMO roles. Domain Controller #1 Place the two forest roles on this server.

Getting Ready # Install Windows 7 from scratch on to your test machine. DO NOT upgrade from Windows XP, this needs to be a fresh install. Customise Windows 7 with any software, security settings or general settings you wish. When you install from this image all the settings as well as user accounts will be installed by default. Install WAIK for 7/2008 on the test PC. Download from here (1.7GB). Create WINPE Disk # Right click command prompt run as admin Change to directory “C:Program FilesWindows AIKToolsPETools” run command “copype x86 c:winpe” run command “imagex /mountrw c:winpewinpe.wim 1 c:winpemount” copy imagex.exe from “C:Program FilesWindows AIKToolsx86imagex.exe” to “c:winpemountwindowssystem32″ Create wimscript.ini in “c:winpemountwindowssystem32″ with following inside [ExclusionList] ntfs.log hiberfil.sys pagefile.sys "System Volume Information" RECYCLER WindowsCSC [CompressionExclusionList] *.mp3 *.zip *.cab WINDOWSinf*.pnf Run Command “imagex.exe /unmount /commit c:winpemount” Run Command “copy c:winpewinpe.wim c:winpeisosourcesboot.wim /y” Run Command “oscdimg -n -h -bc:winpeetfsboot.com c:winpeiso c:winpewinpe.iso” This will create an ISO in c:winpewinpe.iso. Burn this and keep. Now we need to sysprep our machine. (You can remove WAIK and any files you don’t need, test your iso first!) Sysprep Your Machine

Windows Crash Dump analysis is a fairly expansive topic that ranges from simple post mortem analysis of small memory dump files to remote debugging of a live system and probing the failure as it occurs in the operating system. This series of posts will cover analysis and troubleshooting of many common failures faced by end users on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, and Windows 8. This specific post examines memory dumps, how to install/use the tools to analyze them, crashes that appear when KeBugCheckEx is called, and initial steps with most dumps. The blue screen of death in Windows 7 and earlier versions of Windows: “A problem has been detected and Windows has been shut down to prevent damage to your computer.” The blue screen of death in Windows 8 Developer Preview: “Your PC ran into a problem that it couldn’t handle, and now it needs to restart. You can search for the error online: %s.”