Launch Admin Tools from the Command Line

This list of .msc files will help you run admin tools from the command line.


Most admin tools in Windows Server 2003 are MMC consoles you can access from the Start menu. But you can also open these console from the command line if you know their .msc filenames. This can be especially useful if you log on to your admin workstation using a limited privilege account and use Runas to perform admin tasks. For reference, here's a list of admin tools with their associated .msc files. You can print this out and tape it on the wall beside your workstation until you memorize the ones you use most commonly.

http://www.windowsnetworking.com/kbase/windowstips/windows2003/admintips/admin/launchadmintoolsfromthecommandline.html
AD Domains and Trusts
domain.msc

Active Directory Management
admgmt.msc

AD Sites and Serrvices
dssite.msc

AD Users and COmputers
dsa.msc

ADSI Edit
adsiedit.msc

Authorization manager
azman.msc

Certification Authority Management
certsrv.msc

Certificate Templates
certtmpl.msc

Cluster Administrator
cluadmin.exe

Computer Management
compmgmt.msc

Component Services
comexp.msc

Configure Your Server
cys.exe

Device Manager
devmgmt.msc

DHCP Managment
dhcpmgmt.msc

Disk Defragmenter
dfrg.msc

Disk Manager
diskmgmt.msc

Distributed File System
dfsgui.msc

DNS Managment
dnsmgmt.msc

Event Viewer
eventvwr.msc

Indexing Service Management
ciadv.msc

IP Address Manage
ipaddrmgmt.msc

Licensing Manager
llsmgr.exe

Local Certificates Management
certmgr.msc

Local Group Policy Editor
gpedit.msc

Local Security Settings Manager
secpol.msc

Local Users and Groups Manager
lusrmgr.msc

Network Load balancing
nlbmgr.exe

Performance Montior
perfmon.msc

PKI Viewer
pkiview.msc

Public Key Managment
pkmgmt.msc

QoS Control Management
acssnap.msc

Remote Desktops
tsmmc.msc

Remote Storage Administration
rsadmin.msc

Removable Storage
ntmsmgr.msc

Removalbe Storage Operator Requests
ntmsoprq.msc

Routing and Remote Access Manager
rrasmgmt.msc

Resultant Set of Policy
rsop.msc

Schema management
schmmgmt.msc

Services Management
services.msc

Shared Folders
fsmgmt.msc

SID Security Migration
sidwalk.msc

Telephony Management
tapimgmt.msc

Terminal Server Configuration
tscc.msc

Terminal Server Licensing
licmgr.exe

Terminal Server Manager
tsadmin.exe

UDDI Services Managment
uddi.msc

Windows Mangement Instumentation
wmimgmt.msc

WINS Server manager
winsmgmt.msc

Find the Service tag or Serial number of VMware ESX host

There might be a few reasons that you would need to do this. But if you need to locate the Serial Number of server or Service Tag of your Dell server you can do this from the service console command line. In the past I have needed this to schedule service and also to confirm the identity of a server for the Vendor that was on site. In case you do not have a database to reference or maybe someone mistyped the digits you can always fall back to this method.
Type the following command from the command line on the service console and you will get some Vendor details and serial number information.

[root@host name]# /usr/sbin/dmidecode |grep -A4 “System Information”

inetpub\logs\logfiles\w3svc1 getting very large

http://social.technet.microsoft.com/Forums/en/configmgrgeneral/thread/d989b249-0159-41fc-b78c-1f1d91ce8bb3

Logfiles can be deleted / trimmed with the following command which creates a scheduled task to do it :-


at 12:00 /EVERY:Su Forfiles.exe -p C:\WINDOWS\system32\LogFiles\W3SVC1 -m *.log -d -30 -c \"Cmd.exe /C del @path\"

------------------------------------------------------
IIS logging is is enabled by default in IIs& ad IIS7.5 so I assume that you mean one of those: http://technet.microsoft.com/en-us/library/cc754631(WS.10).aspx.


Here we can disable the IIS log files


Go To IIS console -> and Right click WebSite Property and click web site TAB find the Enable logging Next Step ->Uncheck the Enable Logging and restart the IISADMIN services after restart the service IIS log files are disbled






--------------------------------------------------------------------------------

How to check Oracle version / hvordan sjekke Oracle versjon?

SQL> connect system/manager@ as sysdba;

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle9i Release 9.2.0.1.0 - Production
PL/SQL Release 9.2.0.1.0 - Production
CORE 9.2.0.1.0 Production
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production

SQL>

Fix på problem med ESX-host som har "disconnect" status i VirtualCenter

[root@tro-bl-esx02 root]# service mgmt-vmware restart
Stopping VMware ESX Server Management services:
VMware ESX Server Host Agent Watchdog [ OK ]
VMware ESX Server Host Agent [ OK ]
Starting VMware ESX Server Management services:
VMware ESX Server Host Agent (background) [ OK ]
Availability report startup (background) [ OK ]

[root@tro-bl-esx02 root]# service vmware-vpxa restart
Stopping vmware-vpxa: [ OK ]
Starting vmware-vpxa: [ OK ]
[root@tro-bl-esx02 root]#

How to upgrade iLO Firmware on c7000 blades

1. Last ned fila CP013601.scexe fra HP >> CP013601.scexe
2. Logg inn som root på ESX-server
3.Gi rettigheter til å kjøre fila >> chmod +x CP013601scexe
4. Bekreft oppgradering av firmware.
5. iLO firmware er oppgraert :-)

-----------------------------

[root@tro-bl-esx01 tmp]# chmod +x CP013601.scexe
[root@tro-bl-esx01 tmp]# ./CP013601.scexe

FLASH_iLO2 v1.12 for Linux (Aug 31 2009)
Copyright 2009 Hewlett-Packard Development Company, L.P.
Firmware image: ilo2_201.bin
Current iLO 2 firmware version  1.70; Serial number ILOCZJ80504HC

Component XML file: CP013601.xml
CP013601.xml reports firmware version 2.01
This operation will update the firmware on the
iLO 2 in this server with version 2.01.
Continue (y/N)?y
Current firmware is 1.70 (Dec 02 2008 17:50:39)
Firmware image is 0x300000 bytes
Committing to flash part...
******** DO NOT INTERRUPT! ********
Flashing completed!                                  
Attempting to reset device.
Succeeded.
Waiting for iLO 2 to reboot...
iLO 2 reboot completed.
[root@tro-bl-esx01 tmp]#

HP SIM Agent Configure on ESXi 4.1

http://communities.vmware.com/message/1590665


There is no HP Agent for ESXi. What you probably installed (at least I hope...) is the CIM offline bundle for HP.

Once you have those installed, you have to configure HP SIM to use WBEM (NOT SNMP) to communicate with the ESXi server. I actually had to do this very recently and documented it. See below:

1) Make sure the HP CIM bundle is installled. To do this, either install ESXi with the HP version of ESXi, or install the offline bundle downloaded from HPs site. To install the offline bundle:

1) Log onto VMWare VC Server
2) Go to Start Menu and Launch the VMWare CLI
3) Cd to the bin directory: c:\program files (x86)\Vmware\VmWAre vSphere CLI\bin

To Verify what patches in the bundle apply to your host:

Vihostupdate.pl --server servername --scan --bundle path to zip bundle

Vihostupdate.pl --server ah-esxi-exch --scan --bundle "C:\ESXi HP\hp-esxi4.1uX-bundle-1.0.zip"

Make

To install:

Vihostupdate.pl --server servername --install --bundle path to zip bundle

Vihostupdate.pl --server ah-esxi-exch --install --bundle "C:\ESXi HP\hp-esxi4.1uX-bundle-1.0.zip"

2) Go to HP SIM, and go to Options -> Discovery.

3) On the discovery screen, create a new discovery task. Add your ESXi hosts to the "Ping inclusion ranges/host names" text box.

4) CLick the blue Credentials button on the bottom (this is important).

5) CLick Show advanced protocol credentials.

6) Click the WBEM/WMI tab.

7) Enter in a valid username and password for your ESXi Host (I use root and the root password).

8) Click OK.

9) Now save the task by clicking Save.

10) Run the task by selecting it's radio button and clicking Run Now.

This should cause it to appear in HP SIM. Now, you need to setup WBEM indications (they replace SNMP traps).

To do this:

1) Log into Insight Manager on AH-Monitor1

2) Go to Options -> Events -> Subscribe to WBEM Events

3) Verify your server is in the Targets list (Click Add Target if necessary).

4) Click Next and finish the wizard to activate these events.

5) Reboot the ESXi Server to have this take effect.