USB Media Bootable

A few simple couple steps are necessary to créate a USB Media Bootable:

1-Now we can create a USB autobootable with this ISO. Connect the USB device and open CMD window and execute Diskpart command

2- Now is needed to list the disk available to know what is the USB disk.

3- And Select de USB disk

4-Clean the USB Disk

5- Create the primary partition

6- Select the new partition

7- Active the partition

8- Format the new usb partition

9- Active the partition and Assign a drive letter

10 – Exit from Diskpart

11- Copy the stand-alone iso files to USB files. Use xcopy with the following sentence where D: is the mounted ISO and G: is the USB drive assign.

xcopy D:\*.* /s /e /f G:\

Now the USB bootable media with a Stand-Alone media is created.

This Picture is an example:

USB Bootable
USB Media Bootable Creation

Enjoy it!

JoanD

 

How to register OCX with SCCM 2012

Today, I’d a new challengue in my Customer. They needed to register a OCX to all their computer clients.

Perfect!! Start the party…

First of all, we need to create a folder in the SCCM repository. Copy in this folder this files and folders:

OCX SCCM Structure folder

Where in the folder OCXFile is located the OCX file. To register the OCX I’ve a cmd file like this one (RegisterOCX.bat):

@echo off

xcopy .\OCXFile\*.* “%programfiles(x86)%\FolderOCX” /e /c /i /g /h > nul

regsvr32 /s “%programfiles(x86)%\FolderOCX\OCXFile.ocx”

And to unregister the OCX I’ve this other cmd file (UnregisterOCX.bat):

@echo off

regsvr32 /u /s “%programfiles(x86)%\FolderOCX\OCXFile.ocx”

rd /S /Q “%programfiles(x86)%\FolderOCX”

Now, we only need to create a Application:

-Application with manually specify the aplication information

-Add a Deployment Type Manually, and with Type “Script Installer”

-Select Content Location. Folder created first of all.

-Select in “Installation Program” the RegisterOCX.bat

-Select in “Uninstall Program” the UnregisterOCX.bat

-Add a Clause to detect if the package is or not installed. For example, if exist the file ocx in the “%ProgramFiles(x86)%\folderOCX”

-Follow the wizard

Now, we can distribute the package to DP, and deploy to the target collection to install (register) or uninstall (unregister).

Enjoy,

JoanD

 

Windows Installer Exit Codes

If you are trying to deploy or install a MSI with MSIEXEC this list of exit codes are very usefull:

Value Description Error Code
0 Action completed successfully. ERROR_SUCCESS
13 The data is invalid. ERROR_INVALID_DATA
87 One of the parameters was invalid. ERROR_INVALID_PARAMETER
120 This function is not available for this platform. It is only available on Windows 2000 and Windows XP with Window Installer version 2.0. ERROR_CALL_NOT_IMPLEMENTED
1259 This error code only occurs when using Windows Installer version 2.0 and Windows XP or later. If Windows Installer determines a product may be incompatible with the current operating system, it displays a dialog informing the user and asking whether to try to install anyway. This error code is returned if the user chooses not to try the installation. ERROR_APPHELP_BLOCK
1601 The Windows Installer service could not be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered. ERROR_INSTALL_SERVICE_FAILURE
1602 User cancel installation. ERROR_INSTALL_USEREXIT
1603 Fatal error during installation. ERROR_INSTALL_FAILURE
1604 Installation suspended, incomplete. ERROR_INSTALL_SUSPEND
1605 This action is only valid for products that are currently installed. ERROR_UNKNOWN_PRODUCT
1606 Feature ID not registered. ERROR_UNKNOWN_FEATURE
1607 Component ID not registered. ERROR_UNKNOWN_COMPONENT
1608 Unknown property. ERROR_UNKNOWN_PROPERTY
1609 Handle is in an invalid state. ERROR_INVALID_HANDLE_STATE
1610 The configuration data for this product is corrupt. Contact your support personnel. ERROR_BAD_CONFIGURATION
1611 Component qualifier not present. ERROR_INDEX_ABSENT
1612 The installation source for this product is not available. Verify that the source exists and that you can access it. ERROR_INSTALL_SOURCE_ABSENT
1613 This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. ERROR_INSTALL_PACKAGE_VERSION
1614 Product is uninstalled. ERROR_PRODUCT_UNINSTALLED
1615 SQL query syntax invalid or unsupported. ERROR_BAD_QUERY_SYNTAX
1616 Record field does not exist. ERROR_INVALID_FIELD
1618 Another installation is already in progress. Complete that installation before proceeding with this install. ERROR_INSTALL_ALREADY_RUNNING
1619 This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. ERROR_INSTALL_PACKAGE_OPEN_FAILED
1620 This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. ERROR_INSTALL_PACKAGE_INVALID
1621 There was an error starting the Windows Installer service user interface. Contact your support personnel. ERROR_INSTALL_UI_FAILURE
1622 Error opening installation log file. Verify that the specified log file location exists and is writable. ERROR_INSTALL_LOG_FAILURE
1623 This language of this installation package is not supported by your system. ERROR_INSTALL_LANGUAGE_UNSUPPORTED
1624 Error applying transforms. Verify that the specified transform paths are valid. ERROR_INSTALL_TRANSFORM_FAILURE
1625 This installation is forbidden by system policy. Contact your system administrator. ERROR_INSTALL_PACKAGE_REJECTED
1626 Function could not be executed. ERROR_FUNCTION_NOT_CALLED
1627 Function failed during execution. ERROR_FUNCTION_FAILED
1628 Invalid or unknown table specified. ERROR_INVALID_TABLE
1629 Data supplied is of wrong type. ERROR_DATATYPE_MISMATCH
1630 Data of this type is not supported. ERROR_UNSUPPORTED_TYPE
1631 The Windows Installer service failed to start. Contact your support personnel. ERROR_CREATE_FAILED
1632 The temp folder is either full or inaccessible. Verify that the temp folder exists and that you can write to it. ERROR_INSTALL_TEMP_UNWRITABLE
1633 This installation package is not supported on this platform. Contact your application vendor. ERROR_INSTALL_PLATFORM_UNSUPPORTED
1634 Component not used on this machine ERROR_INSTALL_NOTUSED
1635 This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package. ERROR_PATCH_PACKAGE_OPEN_FAILED
1636 This patch package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer patch package. ERROR_PATCH_PACKAGE_INVALID
1637 This patch package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. ERROR_PATCH_PACKAGE_UNSUPPORTED
1638 Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. ERROR_PRODUCT_VERSION
1639 Invalid command line argument. Consult the Windows Installer SDK for detailed command line help. ERROR_INVALID_COMMAND_LINE
1640 Installation from a Terminal Server client session not permitted for current user. ERROR_INSTALL_REMOTE_DISALLOWED
1641 The installer has started a reboot. This error code not available on Windows Installer version 1.0. ERROR_SUCCESS_REBOOT_INITIATED
1642 The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch. This error code is not available on Windows Installer version 1.0. ERROR_PATCH_TARGET_NOT_FOUND
1643 The patch package is not permitted by system policy. This error code is available with Windows Installer versions 2.0 or later. ERROR_PATCH_PACKAGE_REJECTED
1644 One or more customizations are not permitted by system policy. This error code is available with Windows Installer versions 2.0 or later. ERROR_INSTALL_TRANSFORM_REJECTED
3010 A reboot is required to complete the install. This does not include installs where the ForceReboot action is run. This error code not available on Windows Installer version 1.0. ERROR_SUCCESS_REBOOT_REQUIRED

I enjoy it.

JoanD

Best Practices WSUS

Best Practices for WSUS

I only want to attach two link to the best practices for WSUS 3.0 and WSUS 2.0. On the same place yo can find a complet guide about WSUS operations.

Best Practices with Windows Server Update Services 3.0

http://technet.microsoft.com/en-us/library/cc720525(WS.10).aspx

 

Best Practices with Windows Server Update Services 2.0

http://technet.microsoft.com/en-us/library/cc708536(WS.10).aspx

I hope that this will do very interesting for the community.

See you the next time.

Joan

Remove Cluster Ex2k3

How to remove a Exchange 2003 Cluster

If you are planning remove a Exchange 2003 cluster is possible that you need a procedure o guide to do it.

In this post, I write a step list to do this task. This is a general procedure, also, in some scenarios is possible that you need to modify it. But I think this is a good general procedure/guide to know how to remove a exchange 2003 cluster.

Here is the detailed procedure for the removal of exchange form cluster (A/A)

  1. Move all resources to second node (Cluster and Exchange VS)
  2. From Ex2K3 CD, run setup.exe and remove exchange gracefully, when you get “Removing Exchange from the last node”, answer NO.

Follow following this link

How to Uninstall Exchange Server 2003
http://technet.microsoft.com/en-us/library/bb125110.aspx

If for any reason could not remove exchange gracefully; follow the KB on

How to remove exchange manually
http://support.microsoft.com/?id=833396

  1. From cluster administrator Right-click on the node to be removed then stop cluster service
  2. From the other node select the first node and then right-click again and evict the node.
  3. From Add/Remove Programs, Windows component, uncheck “Cluster Service”, Next (This will remove cluster service and reboot the server)
  4. Then we have to remove the exchange from first node.

Follow the following link for the same

How to  Remove an Exchange Virtual Server from an Exchange Cluster
http://technet.microsoft.com/en-us/library/aa996239.aspx

  1. Take the Exchange System Attendant resource offline.

For detailed information, see How to Take the Exchange System Attendant Resource Offline

How to Take the Exchange System Attendant Resource Offline
http://technet.microsoft.com/en-us/library/aa998788.aspx

  1. Remove the Exchange Virtual Server

For detailed information, see How to Remove an Exchange Virtual Server Using Cluster Administrator

How to Remove an Exchange Virtual Server Using Cluster Administrator
http://technet.microsoft.com/en-us/library/bb123928.aspx

  1. Delete remaining cluster resources

For detailed information, see How to Delete the Remaining Resources After Removing an Exchange Virtual Server

How to Delete the Remaining Resources After Removing an Exchange Virtual Server
http://technet.microsoft.com/en-us/library/bb123742.aspx

  1. Now from the exchange setup CD onto to first node and uninstall the exchange binaries.

If for any reason could not remove exchange gracefully; follow the KB on

How to remove exchange manually
http://support.microsoft.com/?id=833396

  1. Check in ADSIEDIT if you still have the server listed in following location. Confirm again and delete the virtual server.

Open ADSIEDIT

Expand Configuration -> Services -> Microsoft Exchange -> ORG Name -> Administrative Group -> your Admin group name -> Servers

Enjoy it

Joan