http://admodify.codeplex.com/
Monday, October 12, 2009
(Freeware) ADModify.NET - modify multiple user accounts in Active Directory
http://admodify.codeplex.com/
hMailServer is a free e-mail server for Microsoft Windows
It supports the common e-mail protocols (IMAP, SMTP and POP3) and can easily be integrated with many existing web mail systems. It has flexible score-based spam protection and can attach to your virus scanner to scan all incoming and outgoing email.
hMailServer is a free e-mail server for Microsoft Windows
Windows add the Free SSL Cert - StartCom to root certificates
StartCom, the vendor and distributor of StartCom Linux Operating Systems, also operates MediaHost™, a hosting company, which offered its clients, SSL secured web sites with certificates signed by StartCom for many years. That's where the idea originated: Free SSL certificates!
http://cert.startcom.org/
Windows add the Free SSL Cert - StartCom to root certificates
Sunday, October 11, 2009
Eventcreate - Enables an administrator to create a custom event in a specified event log.
Enables an administrator to create a custom event in a specified event log.
Syntax
eventcreate [/s Computer [/u Domain\User [/p Password]] {[/l {APPLICATION|SYSTEM}]|[/so SrcName]} /t {ERROR|WARNING|INFORMATION|SUCCESSAUDIT|FAILUREAUDIT} /id EventID /d Description
Parameters
/s Computer : Specifies the name or IP address of a remote computer (do not use backslashes). The default is the local computer.
/u Domain \ User : Runs the command with the account permissions of the user specified by User or Domain\User. The default is the permissions of the current logged on user on the computer issuing the command.
/p Password : Specifies the password of the user account that is specified in the /u parameter.
/l { APPLICATION | SYSTEM } : Specifies the name of the event log where the event will be created. The valid log names are APPLICATION and SYSTEM.
/so SrcName : Specifies the source to use for the event. A valid source can be any string and should represent the application or component that is generating the event.
/t { ERROR | WARNING | INFORMATION | SUCCESSAUDIT | FAILUREAUDIT } : Specifies the type of event to create. The valid types are ERROR, WARNING, INFORMATION, SUCCESSAUDIT, and FAILUREAUDIT.
/id EventID : Specifies the event ID for the event. A valid ID is any number from 1 to 65535.
/d Description : Specifies the description to use for the newly created event.
/? : Displays help at the command prompt.
Remarks
- Custom events cannot be written to the security log.
Examples
The following examples show how you can use the eventcreate command:
eventcreate /t error /id 100 /l application /d "Create event in application log"
eventcreate /t information /id 1000 /so winmgmt /d "Create event in WinMgmt source"
eventcreate /t error /id 2001 /so winword /l application /d "new src Winword in application log"
eventcreate /s server /t error /id 100 /l application /d "Remote machine without user credentials"
eventcreate /s server /u user /p password /id 100 /t error /l application /d "Remote machine with user credentials"
eventcreate /s server1 /s server2 /u user /p password /id 100 /t error /so winmgmt /d "Creating events on Multiple remote machines"
eventcreate /s server /u user /id 100 /t warning /so winmgmt /d "Remote machine with partial user credentials"
Formatting legend
Format | Meaning |
---|---|
Italic | Information that the user must supply |
Bold | Elements that the user must type exactly as shown |
Ellipsis (...) | Parameter that can be repeated several times in a command line |
Between brackets ([]) | Optional items |
Between braces ({}); choices separated by pipe (|). Example: {even|odd} | Set of choices from which the user must choose only one |
Courier font | Code or program output |
Eventcreate - Enables an administrator to create a custom event in a specified event log.
vAlarm - Free Desktop Tool for Monitoring vCenter Alarms
The product is designed to be installed on an administrators PC, and provides automated monitoring of vCenter alarms without needing to be logged into a full VI Client console.
The software automatically communicates with a vCenter server on a user configurable schedule, and notifies any active alarms via a popup information bubble in the notification area of a users desktop.
The option to show details of all active alarms displays an information dialogue which lists individual alarms with detailed descriptions.
The software supports VMware vCenter 2.5 & 4.0.
http://xtravirt.com/xd10130
vAlarm - Free Desktop Tool for Monitoring vCenter Alarms
Physical to Virtual Conversion – Disk2Vhd
http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx
Physical to Virtual Conversion – Disk2Vhd
Grant root privilege to user account in RHEL
1. create the user account call "normaluser"
# useradd -d /home/user normaluser
2. then as root run:
# su -
# visudo
3. in the file you will see
root ALL=(ALL) ALL
4. add a line below that line that has
normaluser ALL=(ALL) ALL
* replace "normaluser" with the username you want.
then when you want to do some admin level work you would just use "sudo" before the command.
e.g. sudo /sbin/shutdown -r now
Grant root privilege to user account in RHEL
Configuring the Boot Loader to boot the old kernel
Configuring the Boot Loader
Now that you have recompiled your kernel, you must configure the boot loader to boot the new kernel. This is a crucial step. If you do not perform this step or if you perform it incorrectly, you will not be able to boot your system. If this happens, boot your system with the boot diskette you created earlier and try configuring the boot loader again. If your boot diskette does not work, refer to Chapter 3 for more information about rescue mode.
In order to provide a redundant boot source to protect from a possible error in a new kernel, you should keep the original kernel available. During the installation of Red Hat Linux 7.3, you had the option to choose either GRUB or LILO as your boot loader. Refer to the appropriate section that follows.
GRUB
If you selected GRUB as your boot loader, modify /boot/grub/grub.conf. The default GRUB configuration file looks similar to the following:
# NOTICE: You have a /boot partition. This means that |
If you created a separate /boot partition, the paths to the kernel and initrd image are relative to the /boot partition.
To add your new kernel to GRUB, copy the existing title section to a new one and modify it to boot your new kernel image (and initrd image if you have any SCSI devices and have created an initrd image). Be sure the title of the new section is different from the title of the section to boot the old kernel. By default, Red Hat Linux uses Red Hat Linux and the kernel version in parentheses to differentiate between different kernels for GRUB to boot. In our example, the new /boot/grub/grub.conf file would look like the following:
# NOTICE: You have a /boot partition. This means that |
The default boot entry is set to number 0. To make your new kernel the default, either place its section first or change the default entry number to the appropriate number (remember that it starts counting with 0). For GRUB, you do not need to run any commands after modifying the configuration file.
From now on, when the system boots you will see the following GRUB boot options:
Red Hat Linux (2.4.18-0.12-jul2001) |
To boot the default kernel, press [Enter] or wait for it to time out. If you want to boot the old kernel, select it and press [Enter].
You can begin testing your new kernel by rebooting your computer and watching the messages to ensure that your hardware is detected properly.
LILO
To configure LILO to boot the new kernel, you need to update the /etc/lilo.conf file and run the command /sbin/lilo -v.
The default /etc/lilo.conf file looks similar to the following:
boot=/dev/hda |
To add your new kernel to LILO, copy the existing image section to a new one and modify it to boot your new kernel image (and initrd image if you have any SCSI devices and have created an initrd image). Also, rename the label of the old kernel to something such as linux-old. Your /etc/lilo.conf should look similar to the following:
boot=/dev/hda |
To activate your changes, run the command /sbin/lilo -v. If all goes well, you will see output similar to the following:
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger |
Be sure the messages contains Writing boot sector. The * after linux means that the section labeled linux is the default kernel that LILO will boot.
From now on, when the system boots you will see linux and linux-old as LILO boot options.
To boot the new kernel (linux) simply press [Enter], or wait for LILO to time out. If you want to boot the old kernel (linux-old), select linux-old and press [Enter].
You can begin testing your new kernel by rebooting your computer and watching the messages to ensure your hardware is detected properly.
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/s1-custom-kernel-bootloader.html
Configuring the Boot Loader to boot the old kernel
Searching, Downloading, and Installing Updates via VBS
Set updateSession = CreateObject("Microsoft.Update.Session")
Set updateSearcher = updateSession.CreateupdateSearcher()
WScript.Echo "Searching for updates..." & vbCRLF
Set searchResult = _
updateSearcher.Search("IsInstalled=0 and Type='Software'")
WScript.Echo "List of applicable items on the machine:"
For I = 0 To searchResult.Updates.Count-1
Set update = searchResult.Updates.Item(I)
WScript.Echo I + 1 & "> " & update.Title
Next
If searchResult.Updates.Count = 0 Then
WScript.Echo "There are no applicable updates."
WScript.Quit
End If
WScript.Echo vbCRLF & "Creating collection of updates to download:"
Set updatesToDownload = CreateObject("Microsoft.Update.UpdateColl")
For I = 0 to searchResult.Updates.Count-1
Set update = searchResult.Updates.Item(I)
WScript.Echo I + 1 & "> adding: " & update.Title
updatesToDownload.Add(update)
Next
WScript.Echo vbCRLF & "Downloading updates..."
Set downloader = updateSession.CreateUpdateDownloader()
downloader.Updates = updatesToDownload
downloader.Download()
WScript.Echo vbCRLF & "List of downloaded updates:"
For I = 0 To searchResult.Updates.Count-1
Set update = searchResult.Updates.Item(I)
If update.IsDownloaded Then
WScript.Echo I + 1 & "> " & update.Title
End If
Next
Set updatesToInstall = CreateObject("Microsoft.Update.UpdateColl")
WScript.Echo vbCRLF & _
"Creating collection of downloaded updates to install:"
For I = 0 To searchResult.Updates.Count-1
set update = searchResult.Updates.Item(I)
If update.IsDownloaded = true Then
WScript.Echo I + 1 & "> adding: " & update.Title
updatesToInstall.Add(update)
End If
Next
WScript.Echo vbCRLF & "Would you like to install updates now? (Y/N)"
strInput = WScript.StdIn.Readline
WScript.Echo
If (strInput = "N" or strInput = "n") Then
WScript.Quit
ElseIf (strInput = "Y" or strInput = "y") Then
WScript.Echo "Installing updates..."
Set installer = updateSession.CreateUpdateInstaller()
installer.Updates = updatesToInstall
Set installationResult = installer.Install()
'Output results of install
WScript.Echo "Installation Result: " & _
installationResult.ResultCode
WScript.Echo "Reboot Required: " & _
installationResult.RebootRequired & vbCRLF
WScript.Echo "Listing of updates installed " & _
"and individual installation results:"
For I = 0 to updatesToInstall.Count - 1
WScript.Echo I + 1 & "> " & _
updatesToInstall.Item(i).Title & _
": " & installationResult.GetUpdateResult(i).ResultCode
Next
End If
http://msdn.microsoft.com/en-us/library/aa387102(VS.85).aspx
Searching, Downloading, and Installing Updates via VBS
Windows Update checklist
http://www3.telus.net/dandemar/updtcl.htm
Windows Update checklist
Wednesday, October 7, 2009
Free SSH server for Windows
MobaSSH allows you to run commands and transfer files on a remote Windows PC from any operating system (GNU/Linux, Unix, HP-UX, AIX, Windows, ...) through a fully secured and encrypted network connection. MobaSSH is 100% compatible with the Linux/Unix/HPUx/AIX SSH clients, but also with Putty or WinSCP on Windows. |
MobaSSH key features :
- Execute commands on a remote Windows computer
- Transfer files through an encrypted channel
- Retrieve information about the remote computer
- Make backups of your computers over the network
- Silently install software on remote Windows computers
- Silently administer the remote Windows computer (the user can stay connected: the commands are run in background mode)
MobaSSH Home is very simple: after downloading the installer, you can configure and start SSH server on your Windows PC in a single click !
http://mobassh-en.mobatek.net/
Free SSH server for Windows
FREE Stuff for Sharepoint 2007
http://www.expertsharepointconsulting.com/Free-Standard-SharePoint-Master-Pages.aspx
Free WebParts:
http://www.amrein.com/apps/page.asp?Q=5728
http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d%2D183c%2D4fc2%2D8320%2Dba5369008acb&ID=234
http://www.sharepointhq.com/products/free_webparts.htm
http://www.codeplex.com/site/search?projectSearchText=webpart&sortBy=Relevance&licenses=|&refinedSearch=true&page=4
FREE Stuff for Sharepoint 2007
Comparison chart between Windows 7, Windows Vista SP1, and Windows XP SP3
http://www.microsoft.com/downloads/details.aspx?familyid=FA0177CC-7E82-4993-B0D6-FEC84216DD9C&displaylang=en
Comparison chart between Windows 7, Windows Vista SP1, and Windows XP SP3
How to cancel a print job that hangs under Vista and XP
First, you have to stop the Print Spooler Service for this go to Start, then Run and type in services.msc. Scroll down to the Print Spooler service, right-click on it and choose Stop then you have to delete all files under C:\WINDOWS\System32\spool\PRINTERS. Once you’ve restarted the Spooler Service, you might have to press F5 in the print queue applet to make the hanging print job disappear
Method 2
1. Cancel the job (it then hangs at the ‘Deleting – Printing’ stage)
2. At the command prompt, enter: net stop spooler
3. Then enter: net start spooler
4. Bref F5 to refresh the status of the print queue
Source:
http://www.windowsreference.com/windows-vista/how-to-cancel-a-print-job-that-hangs-under-vista-and-xp/
How to cancel a print job that hangs under Vista and XP
How to manage multiple Exchange mailbox accounts in Outlook
To log on to one e-mail account (account A) and to have access to the mailbox for a different e-mail account (account B), follow these steps, as appropriate for the version of Outlook that you are running.
Note These steps assume that both accounts are on the same Exchange server.
Microsoft Outlook 2002 and Microsoft Office Outlook 2003 Users
- Start Outlook with a profile that is configured for the Exchange Server mailbox for account B. You may have to log on to the network as the user of account B for proper validation.
- On the Tools menu, click Options.
- On the Delegates tab, click Add.
- Type or select the name for the user of account A, click Add, and then click OK.
- In all lists, in the Delegate Permissions dialog box, click to select Editor (can read, create, and modify items).
- Click OK two times.
- If the Folder list is not visible, click Folder List on the View menu.
- Right-click Mailbox – user name, and then click Properties for ‘Mailbox – user name on the shortcut menu.
- On the Permissions tab, click Add.
- Type or select the name for the user of account A, click Add, and then click OK.
- In the Name box, click the newly added entry for account A.
- In the Roles box, click Owner, and then click OK.
- Repeat steps 8 through 12 for all the other folders in the mailbox.
- On the File menu, click Exit and Log Off.
- Restart Microsoft Windows, and then log on as the user of account A.
- Start Outlook with a profile that is configured for the Exchange Server mailbox for account A.
- On the Tools menu, click E-mail Accounts.
- Click View or change existing e-mail accounts.
- Click to select Microsoft Exchange Server, and then click Change.
- Click the More Settings button.
- Click the Advanced tab.
- Click Add.
- Type the name for the user of account B, and then click OK three times.
The mailbox for account B appears in your Folder List.
Microsoft Office Outlook 2007 Users
- Start Outlook with a profile that is configured for the Exchange Server mailbox for account B. You may have to log on to the network as the user of account B for proper validation.
- On the Tools menu, click Options.
- On the Delegates tab, click Add.
- Type or select the name for the user of account A, click Add, and then click OK.
- In all lists, click to select Editor (can read, create, and modify items) in the Delegate Permissions dialog box.
- Click OK two times.
- If the Folder list is not visible, click Folder List on the View menu.
- Right-click Mailbox – user name, and then click Properties for ‘Mailbox – user name on the shortcut menu.
- On the Permissions tab, click Add.
- Type or select the name for the user of account A, click Add, and then click OK.
- In the Name box, click the newly added entry for account A.
- In the Permission Level box, click Owner, and then click OK.
- Repeat steps 8 through 12 for all the other folders in the mailbox.
- On the File menu, click Exit and Log Off.
- Restart Windows, and then log on as the user of account A.
- Start Outlook with a profile that is configured for the Exchange Server mailbox for account A.
- On the Tools menu, click Account Settings.
- On the E-mail tab, click the name of the account, and then click the Change icon.
- Click the More Settings button.
- Click the Advanced tab.
- Click Add.
- Type the name for the user of account B, and then click OK three times.
- Click Next, click Finish, and then click Close.
The mailbox for account B appears in your Folder List.
The user for account A can send messages and meeting requests on behalf of the user of account B by entering the name of the user for account B in the From Field. These messages contain the names of the users for both account A and account B.
Source from here
How to manage multiple Exchange mailbox accounts in Outlook
Deploying Group Policy Preferences
Group Policy preferences do not require you to install any services on servers. Windows Server 2008 includes Group Policy preferences by default as part of the Group Policy Management Console (GPMC). Administrators will also be able to configure and deploy Group Policy preferences in a Windows Server 2003 environment by installing the Remote Server Administration Tools (RSAT) on a computer running Windows Vista with SP1. Both RSAT and Windows Vista SP1 will be available in the first quarter of 2008.
Although you don’t have to install any services to create GPOs that contain Group Policy preferences, you must deploy the Group Policy preferences client-side extension (CSE) to any client computer to which you want to deploy preferences. The CSE will be available as a separate download from Microsoft. It supports the following Windows versions:
· Windows XP with SP2
· Windows Vista
· Windows Server 2003 with SP1
Windows Server 2008 already includes the CSE.
Deploying Group Policy Preferences
Tuesday, October 6, 2009
Cannot install a Bluetooth device after you install Windows XP Service Pack 2
Method 1: Rename the Bth.inf file
Rename the %WINDIR%\inf\Bth.inf file to Bth.bak before you install or reinstall the third-party device or stack. When you rename the file, you prevent Windows Plug and Play PNP from using that INF file to install the Bluetooth driver that is included with Windows XP SP2. To rename the file, follow these steps:
- Click Start, click Run, type %windir%\inf in the Open box, and then click OK.
- Right-click Bth.inf, and then click Rename.
- Rename Bth.inf to Bth.bak, and then press ENTER.
- Install the third-party Bluetooth driver.
Method 2: Update the Bluetooth driver in Device Manager
To replace the Windows XP SP2 installation of the Bluetooth stack, update the driver in Device Manager. When you do this, specify your third-party driver. To update the driver in Device Manager, follow these steps:
- Click Start, click Run, type devmgmt.msc in the Open box, and then click OK.
- Locate the device.
- Right-click the device, and then click Update Driver.
- Follow the steps that appear on the screen in the Hardware Update Wizard to specify your third-party driver for the Bluetooth device.
http://support.microsoft.com/default.aspx?scid=kb;en-us;840635
Cannot install a Bluetooth device after you install Windows XP Service Pack 2
USBDeview v1.43 - View all installed/connected USB devices on your system
For each USB device, exteneded information is displayed: Device name/description, device type, serial number (for mass storage devices), the date/time that device was added, VendorID, ProductID, and more...
USBDeview also allows you to uninstall USB devices that you previously used, and disconnect USB devices that are currently connected to your computer.
You can also use USBDeview on a remote computer, as long as you login to that computer with admin user.
http://www.nirsoft.net/utils/usb_devices_view.html
USBDeview v1.43 - View all installed/connected USB devices on your system
(Freeware) Microsoft USBView - USB Connection Viewer
USBView is available for download as a .zip file by clicking here.
(Freeware) Microsoft USBView - USB Connection Viewer
Administration and operation reference
Best Practice Guide for Securing Active Directory Installations
Administering Group Policy with Group Policy Management Console
Active Directory Domain Services Operations Guide
Domain Name System (DNS) Service Product Operations Guide
Print Service Product Operations Guide
WINS Service Product Operations Guide
File Service Product Operations Guide
DHCP Service Product Operations Guide
Administration and operation reference
Saturday, October 3, 2009
Copy Autocomplete name list to another computer (outlook.nk2)
Copy Autocomplete name list to another computer (outlook.nk2)
iLO "Remote Console is unavailable. It is already in use by a different client"
When you try to access the ILO Remote Console on some servers you sometimes get the message "Remote Console is unavailable. It is already in use by a different client". But there is no other client connected to the ILO on that server. How can you "reset" the Remote Console connection (from remote) to access the server through the ILO again?
Solve the problen by simply going to "Network setting -> Apply" (no changes to settings and just applying the current configuration)
It disconnect all connections, you may able to connect the remote console now.
iLO "Remote Console is unavailable. It is already in use by a different client"
Configure HP Integrated Lights Out (ILO) IP address
The menu is straightforward and self explanatory. Use the arrow keys to navigate. Select Enter while the Set Defaults option is highlighted to revert back to factory settings.
First, access the Network menu, disable DHCP and change the DNS name
Then configure your static ip settings
Extract from http://808techblog.com/2009/08/configure-hp-integrated-lights.html
For more information of iLO Configuration, please visit http://808techblog.com/2009/08/configure-hp-integrated-lights.html
Configure HP Integrated Lights Out (ILO) IP address
Friday, October 2, 2009
User last logon info on a domain
Joe Richards' GetUserInfo:
http://www.joeware.net/freetools/tools/getuserinfo/index.htm
To see more info in ADUC properties (not for mass reporting, but useful anyway)
http://www.petri.co.il/view_additional_user_information_in_aduc.htm
Usrstat.exe (Windows 2000 Resource Kit)
This command-line tool displays the user name, full name, and last logon date and time for each user in a given domain.
User last logon info on a domain
Microsoft IAS RADIUS for wireless authentication
http://articles.techrepublic.com.com/5100-10878_11-6148579.html
Microsoft IAS RADIUS for wireless authentication