Archive for the ‘System Engineering’ Category

Manage Certificates

October 26, 2016

The tools to manage certificates on your computer

for current user store: certmgr.msc

for local computer store: certlm.msc

or use mmc.exe -> File -> Add/Remove Snap-in -> Certificates
and you can choose the store

Customize Windows Boot menu

July 22, 2016

Customize Windows Boot menu
(the boot.ini file)

Use the bcdedit tool in the command prompt

bcdedit /?

bcdedit /displayorder {key1} {key2}

bcdedit /set {key} parameter “value”

 

Create Virtual Directories In IIS 6

April 4, 2014

Instead of manually edditing the virtual directories in the GUI
You can edit the config file and for instance copy paste from another application.

Windows\system32\inetsrv\config\applicationHost.config

You have to use a 64-bit editor like the Windows7 notepad.exe

What if you have Visual Studio 2008 installed on a 64-bit system? Visual Studio is a 32-bit application, and it runs just fine on a 64-bit system, but unfortunately 32-bit applications cannot open files that are kept in 64-bit-only file paths – and that includes ApplicationHost.config.

Here’s why this happens – ApplicationHost.config is physically located in the following 64-bit-only path:

%SystemDrive%\Windows\System32\Inetsrv\config

The problem is, 32-bit applications are “magically” redirected by the operating system to the following 32-bit file path:

%SystemDrive%\Windows\SysWOW64\Inetsrv\config

So what happens is that each 32-bit application thinks that it’s in the real System32 folder, so when you try to open ApplicationHost.config using File » Open » File… in Visual Studio, you don’t see ApplicationHost.config in the Inetsrv folder. If you attempt to outsmart the system by dragging-and-dropping ApplicationHost.config into Visual Studio from Windows Explorer it doesn’t work; you don’t get any errors, Visual Studio just sits there and stares back at you.

 

Active Directory naming standards

November 8, 2010

Active Directory naming standards supported include

  • NetBIOS names are the account names required for legacy NT environments.  
  • Fully qualified domain name FQDN
    the path to a network object : wmaples.dallas.support.mycompay.com is my fqdn.
  • DN Distinguished names
    every object in AD has a DN. DN follows X.500 naming conventions. The DN is made up of the nodes from the root domain down through the container hierarchy to the object. Using my FQDN name and putting it into ND form:
    DC=com, DC=mycompany, DC=support, OU=dallas, CN=Users CN=wmaples The distinguished name abbreviations are

    • DC domain component
    • OU organizational unit
    • CN common name

    The listing order is always DC (however many), OU (however many), CN (however many).