NLB or Cluster 2012 Print servers

I'd like the ability to cluster/load balance/failover print servers. These would be Server 2012 or 2012 R2 OS. I have searched the forum's and have seen good and bad experiences for clustering and/or NLB'ing. I have been seeing that this type of HA is no
longer supported in server 2012 (or R2) and you should use Hyper-V (VMware only environment here). What other options out there do I have to achieve this? Side note - I do have a Citrix Netscaler but that appears to be an unsupported option. Any help is appreciated.

Hi,
Failover clustering printservers is indeed no longer supported on 2012.
The recommended setup is a single VM that has high availability on VM Host level. The same as VMWare HA. Note the new recommended scenario might offer lower availability as it does not mitigate server reboots or server resource failures.
http://technet.microsoft.com/en-us/library/jj556311.aspx
MCP/MCSA/MCTS/MCITP

Similar Messages

Cannot install agent on 2 2012 Host servers

Hi, i am using SCVMM 2012 SP1 version 3.1.6011.0
i have 2 2012 Datacentre servers, both hyperv hosts, i am unable to install the agent, manually or remotely
i get an error as soon as i run the installer
"There is a problem with this windows installer package. A DLL for this install to completed could not be run. Contatc your support personnel or package vendor"
Visual C++2010 is installed
error from SCVMM
Error (441)
Agent communication is blocked. On SERVER1.company.org, the version of virtualization software or the VMM agent is unsupported.
Recommended Action
Update the agent and virtualization software, and then try the operation again.
it is working fine for all other servers,
any suggestions would be appreciated.
Phil Mason

i have tried the install through the following
msiexec.exe /i vmmAgent.msi /L*V c:\vmmagent_install.log
here is the log
=== Verbose logging started: 10/09/2014 17:01:44 Build type: SHIP UNICODE 5.00.9200.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (AC:DC) [17:01:44:132]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (AC:DC) [17:01:44:132]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (AC:44) [17:01:44:132]: Resetting cached policy values
MSI (c) (AC:44) [17:01:44:132]: Machine policy value 'Debug' is 0
MSI (c) (AC:44) [17:01:44:132]: ******* RunEngine:
           ******* Product: vmmAgent.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (AC:44) [17:01:44:132]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (AC:44) [17:01:44:132]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\vmm\vmmAgent.msi' against software restriction policy
MSI (c) (AC:44) [17:01:44:132]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (AC:44) [17:01:44:132]: SOFTWARE RESTRICTION POLICY: C:\vmm\vmmAgent.msi is not digitally signed
MSI (c) (AC:44) [17:01:44:132]: SOFTWARE RESTRICTION POLICY: C:\vmm\vmmAgent.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (AC:44) [17:01:44:163]: Cloaking enabled.
MSI (c) (AC:44) [17:01:44:163]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (AC:44) [17:01:44:163]: End dialog not enabled
MSI (c) (AC:44) [17:01:44:163]: Original package ==> C:\vmm\vmmAgent.msi
MSI (c) (AC:44) [17:01:44:163]: Package we're running from ==> C:\vmm\vmmAgent.msi
MSI (c) (AC:44) [17:01:44:163]: APPCOMPAT: Compatibility mode property overrides found.
MSI (c) (AC:44) [17:01:44:163]: APPCOMPAT: looking for appcompat database entry with ProductCode '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'.
MSI (c) (AC:44) [17:01:44:163]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (AC:44) [17:01:44:179]: MSCOREE not loaded loading copy from system32
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'TransformsSecure' is 1
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisablePatch' is 0
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'AllowLockdownPatch' is 0
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisableLUAPatching' is 0
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (c) (AC:44) [17:01:44:179]: APPCOMPAT: looking for appcompat database entry with ProductCode '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'.
MSI (c) (AC:44) [17:01:44:179]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (AC:44) [17:01:44:179]: Transforms are not secure.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'c:\vmmagent_install.log'.
MSI (c) (AC:44) [17:01:44:179]: Command Line: CURRENTDIRECTORY=C:\vmm CLIENTUILEVEL=0 CLIENTPROCESSID=13996
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{6A2A3BC7-0C15-472C-BB42-7D879FA490AB}'.
MSI (c) (AC:44) [17:01:44:179]: Product Code passed to Engine.Initialize:           ''
MSI (c) (AC:44) [17:01:44:179]: Product Code from property table before transforms: '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'
MSI (c) (AC:44) [17:01:44:179]: Product Code from property table after transforms: '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'
MSI (c) (AC:44) [17:01:44:179]: Product not registered: beginning first-time install
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (c) (AC:44) [17:01:44:179]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (AC:44) [17:01:44:179]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (AC:44) [17:01:44:179]: Adding new sources is allowed.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: Package name extracted from package path: 'vmmAgent.msi'
MSI (c) (AC:44) [17:01:44:179]: Package to be registered: 'vmmAgent.msi'
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding IsAdminPackage property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisableMsi' is 1
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (AC:44) [17:01:44:179]: User policy value 'AlwaysInstallElevated' is 0
MSI (c) (AC:44) [17:01:44:179]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (c) (AC:44) [17:01:44:179]: Running product '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}' with elevated privileges: Product is assigned.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\vmm'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '13996'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: TRANSFORMS property is now:
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '301'.
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Favorites
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Documents
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Recent
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\SendTo
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Templates
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Local
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Pictures
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Desktop
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (c) (AC:44) [17:01:44:179]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (c) (AC:44) [17:01:44:179]: MSI_LUA: Setting AdminUser property to 1 because this is the client or the user has already permitted elevation
MSI (c) (AC:44) [17:01:44:179]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'IT'.
MSI (c) (AC:44) [17:01:44:179]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'SJOG'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\vmm\vmmAgent.msi'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\vmm\vmmAgent.msi'.
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\vmm\'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\vmm\'.
MSI (c) (AC:DC) [17:01:44:195]: PROPERTY CHANGE: Adding VersionHandler property. Its value is '5.00'.
=== Logging started: 10/09/2014 17:01:44 ===
MSI (c) (AC:44) [17:01:44:195]: Note: 1: 2205 2: 3: PatchPackage
MSI (c) (AC:44) [17:01:44:195]: Machine policy value 'DisableRollback' is 0
MSI (c) (AC:44) [17:01:44:195]: User policy value 'DisableRollback' is 0
MSI (c) (AC:44) [17:01:44:195]: PROPERTY CHANGE: Adding UILevel property. Its value is '5'.
MSI (c) (AC:44) [17:01:44:195]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (c) (AC:44) [17:01:44:195]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (c) (AC:44) [17:01:44:195]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (c) (AC:44) [17:01:44:195]: Doing action: INSTALL
Action 17:01:44: INSTALL.
Action start 17:01:44: INSTALL.
MSI (c) (AC:44) [17:01:44:195]: UI Sequence table 'InstallUISequence' is present and populated.
MSI (c) (AC:44) [17:01:44:195]: Running UISequence
MSI (c) (AC:44) [17:01:44:195]: PROPERTY CHANGE: Adding EXECUTEACTION property. Its value is 'INSTALL'.
MSI (c) (AC:44) [17:01:44:195]: Doing action: FindRelatedProducts
Action 17:01:44: FindRelatedProducts. Searching for related applications
Action start 17:01:44: FindRelatedProducts.
Action ended 17:01:44: FindRelatedProducts. Return value 1.
MSI (c) (AC:44) [17:01:44:195]: Doing action: PrepareDlg
Action 17:01:44: PrepareDlg.
Action start 17:01:44: PrepareDlg.
Info 2898. For WixUI_Font_Normal textstyle, the system created a 'Tahoma' font, in 0 character set, of 13 pixels height.
Info 2898. For WixUI_Font_Bigger textstyle, the system created a 'Tahoma' font, in 0 character set, of 19 pixels height.
Action 17:01:44: PrepareDlg. Dialog created
Action ended 17:01:44: PrepareDlg. Return value 1.
MSI (c) (AC:44) [17:01:44:195]: Doing action: AppSearch
Action 17:01:44: AppSearch. Searching for installed applications
Action start 17:01:44: AppSearch.
AppSearch: Property: VMMSERVER, Signature: VMMServerRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup 3: 2
AppSearch: Property: BITSPORT, Signature: BitsPortRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
AppSearch: Property: WSMANPORT, Signature: WsmanPortRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
AppSearch: Property: NONTRUSTEDMACHINE, Signature: NonTrustedMachineRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
AppSearch: Property: BITSFORCEFILEFLUSH, Signature: BITSForceFileFlushRegistry
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding BITSFORCEFILEFLUSH property. Its value is '#1'.
AppSearch: Property: BITS4, Signature: CheckQMgr
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding BITS4 property. Its value is 'C:\Windows\system32\QMgr.dll'.
AppSearch: Property: FIREWALLENABLED, Signature: FirewallEnabledRegistry
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding FIREWALLENABLED property. Its value is '#0'.
AppSearch: Property: MSIDLL, Signature: CheckMsiDll
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding MSIDLL property. Its value is 'C:\Windows\SysWOW64\msi.dll'.
AppSearch: Property: WINRMSERVICESTARTTYPE, Signature: AgentWinRMStartTypeRegistry
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding WINRMSERVICESTARTTYPE property. Its value is '#2'.
AppSearch: Property: WSMSVC, Signature: CheckWsmSvc
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding WSMSVC property. Its value is 'C:\Windows\SysWOW64\wsmwmipl.dll'.
AppSearch: Property: DMZUSERNAME, Signature: DmzLocalUserRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
Action ended 17:01:44: AppSearch. Return value 1.
MSI (c) (AC:44) [17:01:44:210]: Doing action: LaunchConditions
Action 17:01:44: LaunchConditions. Evaluating launch conditions
Action start 17:01:44: LaunchConditions.
Action ended 17:01:44: LaunchConditions. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: ValidateProductID
Action 17:01:44: ValidateProductID.
Action start 17:01:44: ValidateProductID.
Action ended 17:01:44: ValidateProductID. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: CostInitialize
Action 17:01:44: CostInitialize. Computing space requirements
Action start 17:01:44: CostInitialize.
MSI (c) (AC:44) [17:01:44:226]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'C:\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
Action ended 17:01:44: CostInitialize. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: FileCost
Action 17:01:44: FileCost. Computing space requirements
Action start 17:01:44: FileCost.
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: MsiAssembly
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Class
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Extension
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: TypeLib
Action ended 17:01:44: FileCost. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: CostFinalize
Action 17:01:44: CostFinalize. Computing space requirements
Action start 17:01:44: CostFinalize.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Patch
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Condition
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding MSAppDataFolder property. Its value is 'C:\ProgramData\Microsoft\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding VMMAppDataFolder property. Its value is 'C:\ProgramData\Microsoft\Virtual Machine Manager\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding SYSCENTERDIR property. Its value is 'C:\Program Files\Microsoft System Center 2012\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding CREDENTIALEXPORTDIRECTORY property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding AgentBinDir property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding SetupDir property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding SetupHelpDir property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\help\'.
MSI (c) (AC:44) [17:01:44:226]: Target path resolution complete. Dumping Directory table...
MSI (c) (AC:44) [17:01:44:226]: Note: target paths subject to change (via custom actions or browsing)
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: TARGETDIR , Object: C:\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: WindowsFolder , Object: C:\Windows\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: CommonAppDataFolder , Object: C:\ProgramData\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: MSAppDataFolder , Object: C:\ProgramData\Microsoft\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: VMMAppDataFolder , Object: C:\ProgramData\Microsoft\Virtual Machine Manager\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: ProgramFiles64Folder , Object: C:\Program Files\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: SYSCENTERDIR , Object: C:\Program Files\Microsoft System Center 2012\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: INSTALLDIR , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: CREDENTIALEXPORTDIRECTORY , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: AgentBinDir , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: SetupDir , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: SetupHelpDir , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\help\
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: MsiAssembly
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_`
= `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
Action ended 17:01:44: CostFinalize. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Skipping action: SetInstallModeRemove (condition is false)
MSI (c) (AC:44) [17:01:44:226]: Doing action: GetAllIPAddresses
Action 17:01:44: GetAllIPAddresses.
Action start 17:01:44: GetAllIPAddresses.
MSI (c) (AC:58) [17:01:44:226]: Invoking remote custom action. DLL: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp, Entrypoint: GetAllIPAddresses
MSI (c) (AC:A0) [17:01:44:226]: Cloaking enabled.
MSI (c) (AC:A0) [17:01:44:226]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (AC:A0) [17:01:44:226]: Connected to service for CA interface.
CustomAction GetAllIPAddresses returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (AC:44) [17:01:44:241]: Note: 1: 1723 2: GetAllIPAddresses 3: GetAllIPAddresses 4: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp
Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action GetAllIPAddresses, entry: GetAllIPAddresses, library: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp
MSI (c) (AC:44) [17:01:46:489]: Product: Microsoft System Center Virtual Machine Manager Agent (x64) -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel
or package vendor. Action GetAllIPAddresses, entry: GetAllIPAddresses, library: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp
Action ended 17:01:46: GetAllIPAddresses. Return value 3.
MSI (c) (AC:44) [17:01:46:489]: Doing action: FatalError
Action 17:01:46: FatalError.
Action start 17:01:46: FatalError.
Action 17:01:46: FatalError. Dialog created
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: _RemoveFilePath
MSI (c) (AC:E8) [17:01:46:505]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: BindImage
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: ProgId
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: PublishComponent
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: SelfReg
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Extension
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Font
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Shortcut
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Class
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: TypeLib
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2727 2:
Action ended 17:01:47: FatalError. Return value 2.
Action ended 17:01:47: INSTALL. Return value 3.
MSI (c) (AC:44) [17:01:47:708]: Destroying RemoteAPI object.
MSI (c) (AC:A0) [17:01:47:708]: Custom Action Manager thread ending.
Property(C): DiskPrompt = Microsoft System Center Virtual Machine Manager Agent (x64) Installation [1]
Property(C): UpgradeCode = {87827097-A5CB-4E4F-BB18-76A7B9CC25A2}
Property(C): BITSPORT = 443
Property(C): WSMANPORT = 5985
Property(C): NONTRUSTEDMACHINE = 0
Property(C): BITSFORCEFILEFLUSH = #1
Property(C): BITS4 = C:\Windows\system32\QMgr.dll
Property(C): FIREWALLENABLED = #0
Property(C): MSIDLL = C:\Windows\SysWOW64\msi.dll
Property(C): WINRMSERVICESTARTTYPE = #2
Property(C): WSMSVC = C:\Windows\SysWOW64\wsmwmipl.dll
Property(C): IPAddressChoice = (no choice)
Property(C): INSTALLDIR = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
Property(C): SetupHelpDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\help\
Property(C): SetupDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\
Property(C): AgentBinDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\
Property(C): VMMAppDataFolder = C:\ProgramData\Microsoft\Virtual Machine Manager\
Property(C): CREDENTIALEXPORTDIRECTORY = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
Property(C): LicenseAccepted = 0
Property(C): DistinguishedNameOption = 0
Property(C): WIXUI_INSTALLDIR = INSTALLDIR
Property(C): WixUIRMOption = UseRM
Property(C): ARPNOREPAIR = 1
Property(C): ALLUSERS = 1
Property(C): CreateUser = **********
Property(C): WixUI_InstallMode = InstallComplete
Property(C): SYSCENTERDIR = C:\Program Files\Microsoft System Center 2012\
Property(C): ProgramFiles64Folder = C:\Program Files\
Property(C): TARGETDIR = C:\
Property(C): MSAppDataFolder = C:\ProgramData\Microsoft\
Property(C): CommonAppDataFolder = C:\ProgramData\
Property(C): SourceDir = C:\vmm\
Property(C): VersionNT = 602
Property(C): Privileged = 1
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Microsoft System Center Virtual Machine Manager Agent (x64)
Property(C): ProductVersion = 3.1.6011.0
Property(C): INSTALLLEVEL = 100
Property(C): ARPCONTACT = Microsoft Corporation
Property(C): ARPPRODUCTICON = ProductIcon
Property(C): ARPHELPLINK =
http://go.microsoft.com/fwlink/?LinkId=68951
Property(C): HostRegSubKey = Microsoft System Center Virtual Machine Manager Agent
Property(C): MofFileName = VMMAgent.mof
Property(C): WmiNamespace = scvmm
Property(C): AgentServiceName = SCVMMAgent
Property(C): AgentExeName = vmmAgent.exe
Property(C): AgentFirewallRuleName = VMMAgent
Property(C): BitsPortName = HTTPS
Property(C): WSMANMINVERSION = 5.2.3790.2984
Property(C): DISTINGUISHEDNAMEOPTION = 0
Property(C): IPADDRESSCHOICE = 0
Property(C): DefaultUIFont = WixUI_Font_Normal
Property(C): WixUI_Mode = InstallDir
Property(C): WIXUI_CREDENTIALEXPORTDIR = CREDENTIALEXPORTDIRECTORY
Property(C): WixUI_LicenseAgreementDlg_Next = InstallDirDlg
Property(C): WixUI_LicenseAgreementDlg_Back = WelcomeDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_NextTrusted = VMMPortSettingDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_NextNonTrusted = VMMDNSelectionDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_Back = InstallDirDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_Change = BrowseDlg
Property(C): WixUI_VMMDNSelectionDlg_Next = VMMPortSettingDlg
Property(C): WixUI_VMMDNSelectionDlg_Back = VMMCredentialDirectoryDlg
Property(C): WixUI_VMMPortSettingDlg_Next = VerifyReadyDlg
Property(C): WixUI_VMMPortSettingDlg_Back = VMMCredentialDirectoryDlg
Property(C): IPADDRESS0 = (address 1 N/A)
Property(C): IPADDRESS1 = (address 2 N/A)
Property(C): IPADDRESS2 = (address 3 N/A)
Property(C): IPADDRESS3 = (address 4 N/A)
Property(C): IPADDRESS4 = (address 5 N/A)
Property(C): IPADDRESS5 = (address 6 N/A)
Property(C): IPADDRESS6 = (address 7 N/A)
Property(C): IPADDRESS7 = (address 8 N/A)
Property(C): ErrorDialog = ErrorDlg
Property(C): SecureCustomProperties = ANYVERSION
Property(C): MsiHiddenProperties = CreateUser;DMZPASSWORD
Property(C): Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\
Property(C): MsiLogFileLocation = c:\vmmagent_install.log
Property(C): PackageCode = {6A2A3BC7-0C15-472C-BB42-7D879FA490AB}
Property(C): ProductState = -1
Property(C): PackagecodeChanging = 1
Property(C): IsAdminPackage = 1
Property(C): CURRENTDIRECTORY = C:\vmm
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 13996
Property(C): MsiSystemRebootPending = 1
Property(C): VersionDatabase = 301
Property(C): VersionMsi = 5.00
Property(C): VersionNT64 = 602
Property(C): WindowsBuild = 9200
Property(C): ServicePackLevel = 0
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 3
Property(C): MsiNTSuiteDataCenter = 1
Property(C): WindowsFolder = C:\Windows\
Property(C): WindowsVolume = C:\
Property(C): System64Folder = C:\Windows\system32\
Property(C): SystemFolder = C:\Windows\SysWOW64\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = C:\Users\DATAPA~1\AppData\Local\Temp\
Property(C): ProgramFilesFolder = C:\Program Files (x86)\
Property(C): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(C): CommonFiles64Folder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Users\datapacremote\AppData\Roaming\
Property(C): FavoritesFolder = C:\Users\datapacremote\Favorites\
Property(C): NetHoodFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(C): PersonalFolder = C:\Users\datapacremote\Documents\
Property(C): PrintHoodFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(C): RecentFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Recent\
Property(C): SendToFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\SendTo\
Property(C): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(C): LocalAppDataFolder = C:\Users\datapacremote\AppData\Local\
Property(C): MyPicturesFolder = C:\Users\datapacremote\Pictures\
Property(C): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(C): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(C): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(C): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(C): DesktopFolder = C:\Users\Public\Desktop\
Property(C): FontsFolder = C:\Windows\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): MsiAMD64 = 6
Property(C): Msix64 = 6
Property(C): Intel = 6
Property(C): PhysicalMemory = 131037
Property(C): VirtualMemory = 89588
Property(C): AdminUser = 1
Property(C): MsiTrueAdminUser = 1
Property(C): LogonUser = datapacremote
Property(C): UserSID = S-1-5-21-4197612004-1255000048-2282055192-13349
Property(C): UserLanguageID = 6153
Property(C): ComputerName = SERVERSAN1
Property(C): SystemLanguageID = 6153
Property(C): ScreenX = 1364
Property(C): ScreenY = 706
Property(C): CaptionHeight = 23
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): TextInternalLeading = 3
Property(C): ColorBits = 32
Property(C): TTCSupport = 1
Property(C): Time = 17:01:47
Property(C): Date = 10/09/2014
Property(C): MsiNetAssemblySupport = 4.0.30319.17929
Property(C): MsiWin32AssemblySupport = 6.2.9200.16384
Property(C): RedirectedDllSupport = 2
Property(C): MsiRunningElevated = 1
Property(C): USERNAME = IT
Property(C): COMPANYNAME = SJOG
Property(C): DATABASE = C:\vmm\vmmAgent.msi
Property(C): OriginalDatabase = C:\vmm\vmmAgent.msi
Property(C): SOURCEDIR = C:\vmm\
Property(C): VersionHandler = 5.00
Property(C): UILevel = 5
Property(C): ACTION = INSTALL
Property(C): EXECUTEACTION = INSTALL
Property(C): ROOTDRIVE = C:\
Property(C): CostingComplete = 1
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
=== Logging stopped: 10/09/2014 17:01:47 ===
MSI (c) (AC:44) [17:01:47:724]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Agent (x64). Product Version: 3.1.6011.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success
or error status: 1603.
MSI (c) (AC:44) [17:01:47:724]: Grabbed execution mutex.
MSI (c) (AC:44) [17:01:47:724]: Cleaning up uninstalled install packages, if any exist
MSI (c) (AC:44) [17:01:47:724]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10/09/2014 17:01:47 ===
Phil Mason

Server 2012 Print Server and DNS CNAME - setspn advice

Hi,
I am building a new Server 2012 Print server. What I would like to do is utilise a DNS CNAME when I deploy the printer, rather than its host name.
I have used 'setspn' to accomplish this, running the following command:
setspn -A HOST/<ALIAS> <hostname>
Now when I browse the alias I can see the installed printer. The problem I have is when I then deploy this via Group Policy it uses the servers host name instead, but it does work. If I manually edit
the GPO to reflect the alias name instead it does not deploy the printer. Moreover the indication on the 2012 server has gone so it does not see that it has any printers deployed.
When I browse the computers host name and try to manually install the printer it will state that it is downloading the drivers but never seems to complete. If I browse it's alias and try the same
thing I receive an error stating that it couldn't connect to the printer. The client machine in this instance is Windows 7 SP1 x64.
What am I doing wrong? Any help would be greatly appreciated.
Howard

I've been struggling with the same problem, for a Windows 2012 R2 print server.
I've added SPN entries and registry tweaks (OptionalHostnames, DisableStrictNameChecking, DnsOnWire etc.), but still couldn't connect printers using the alias, even though I could browse shares on the server, using the alias.
While not explicitly covering 2012 R2, this KB article helped me:
KB2546625.
Adding the alias to the local hosts file solved it for me.
Now, I wanted to be sure that I wasn't applying a bunch of unnecessary tweaks, so I went ahead and removed all registry tweaks (including DnsOnWire mentioned in the KB article), the SPN entry for the alias and rebooted - it still works!
In my case, maybe on Windows Server 2012 R2 in general, all that was needed was to add the alias in the local hosts file.

How to get existing (Dlink) printer servers working with Snow Leopard

I have a new macbook. We have two existing Dlink 1260 print servers serving 3 Windows machines. Both connect to our network via CAT5, we have a Buffalo router and cable modem service. One print server has a HP inkjet ands the other has a Canon inkjet printer. I know the IP addresses (static) and TCP ports of the two print servers. Apple's support people told me they arent trained to help me on print servers.
How does one install these print servers in Snow Leopard 10.6?? I am out of ideas other than Geek Squad :>(

I would imagine you need to connect via IP, LPD, put the IP address of the server in for Address and the Port Name in for the Queue.
You will need Postscript drivers for the printers, based on info on the D-Link site.

Printer Queue Settings Mysteriously Reverting Back to Default Settings on 2008 R2 print servers

Printer Queue Settings Mysteriously Reverting Back to Default Settings on 2008 R2 print servers
We have 4 Windows Server 2008 R2 print servers, all of which has the same printer queues installed on them that are utilized by a 3rd party printing program that does a round-robin load balancing scheme.
All printers are a combination of HP and Xerox all running some variation of the HP UPD and the Xerox UPD. Some use the PCL 5 and some use the PCL 6 version determined by age of printer and need.
There are typically two printer queues for each physical printer.
Example:
LOCATION_ROOM
LOCATION_ROOM_TRAY2
The regular queue is ok being left with default setting,
The _TRAY2 queues are set to print to "labels" or "pre-printed" paper type or a specific tray.
From time to time, these _TRAY2 queues will revert back to a factory default state and lose the setting to print to a specific paper type or tray. Sometimes it happens to the _TRAY2 queue on all 4 servers, sometimes just 1 server, etc. No rhyme
or reason.
Disabled Bi-directional options on both the HP and Xerox UPDs per another article on the internet that said bi-directional could cause the printer to send back settings to the driver and cause this issue. Even with this option off, we continue to see
printer _TRAY2 queue settings revert back to factory default and lose their specific paper and tray settings. We have ruled out the possibility that users or other technicians are the ones making these changes so we suspect it is some interaction between
the servers, printer drivers and printers themselves causing the issue.
Any insight would be greatly appreciated.

I'd start by using one of the print drivers included in Windows for a few of the printers and confirm it's the universal driver that is causing the issue.
HP installs some other processes and services on the machine which communicate with the HP devices.
PML and something else. You might want to shut those down and see if these processes are the ones modifying the settings.
Run process monitor to truly identify which processes is causing the modifications.
Alan Morris formerly with Windows Printing Team

Print servers for 30 client Mac Mini Lab

I have a 30 client Mac Mini lab with printing done by 2 networked HP Officejet 8600+ printers w/ 128mb memory. I would like to have a print server that will speed up the printing(kindergarteners can be impatient). A dozen years or so ago there were separate print servers that managed print requests and gave you only 1 queue to keep track of, but I haven't found one lately for 10.5. Will simply routing print requests to our current document server(PowerMac, Intel 2, 500gb) and giving it the 8600s' IP addresses give me the speed boost I need?

Okay, I have been able to recreate the error message by changing the Security Options for the Windows print queue (located in Properties > Ports > Configure Port). By default, the printer queue is set to use an anonymous account for the connection. When I changed the setting to use the "Windows logon name and password", I would get the error "Returning IPP client-error-not-authorized for Print-Job". This message was found in the cups error log, the print queue did not show an error - simply the job would not appear in the print queue and therefore there was no print.
The only problem I then encountered was when I changed the setting back to use the anonymous account, the error continued to occur - again only showing in cups. The only way I could resolve this was to delete the Windows queue, reset the printing system on the Mac and re-add the Canon printer (in my case an iP6000D). Then when I added the printer again on Win7 using the Bonjour Printer Wizard, I was able to print without error.
So, I suggest you first check that the anonymous account is being used on the Vista PC. If it is, then remove the Windows queue and reset the printing system on the Mac. To reset the printing system, Control-click on the Print & Fax > Printer list and select the reset pop-up. This will delete the Mac queue but not the driver. Now you can add the printer again on the Mac and once that is complete, go back to the PC and add the printer again.
One final note. My printer is using v10.26.x of the Canon driver. Version 10.19 was part of the default 10.6.0 install and can be updated to the same v10.26 by downloading the Canon Printer Driver Update v2.2.
Pahu

How to setup a Cluster of 3 servers on weblogic 9.2?

I'm trying to setup a cluster of 3 servers on WebLogic 9.2 on one physical computer.
I managed to startup 3 servers from cmd in windows like this:
startmanagedweblogic BiPublisher1 http://127.0.0.1:7101
startmanagedweblogic BiPublisher2 http://127.0.0.1:7101
startmanagedweblogic BiPublisher3 http://127.0.0.1:7101
Now I can open each of the 3 servers directly from my browser:
http://127.0.0.1:8101/xmlpserver
http://127.0.0.1:9101/xmlpserver
http://127.0.0.1:9501/xmlpserver
My questions are:
How to setup servers so that I can start them automatically from administration console?
How to configure address in administration console through which I will open my application in a browser?
And after that, how to configure that when server on which I work breaks, it automatically restarts application in another server (no need for failover because BI Publisher does not support session replication, I think)?
Do I need machine and virtual host, and what is their purpose? Node manager? Can somebody explain those things? What i did wrong?
I made this in administration console:
Administration console:
SERVERS:
AdminServer:
Name: BIPublisherServer
Listen address: 127.0.0.1
Listen port: 7101
Server1:
Name: BIPublisher1
Machine: tp43
Cluster: BiPublisherCluster
Listen address: 127.0.0.1
Listen port: 8101
Server2:
Name: BIPublisher2
Machine: tp43
Cluster: BiPublisherCluster
Listen address: 127.0.0.1
Listen port: 9101
Server3:
Name: BIPublisher3
Machine: tp43
Cluster: BiPublisherCluster
Listen address: 127.0.0.1
Listen port: 9501
CLUSTERS:
Cluster: BiPublisherCluster
Multicast Address: 237.0.0.101
Multicast port: 8050
VIRTUAL HOSTS:
Name: bicluster
Virtual Host Names: 127.0.0.1
Targets: Clusters: BiPublishercluster: All servers in the cluster
MACHINES:
Name: tp43
DEPLOYMENTS:
Name: xmlpserver
Path: C:\BiPub\xmlpserver.war
Targets: Virtual Hosts: bicluster

You have some reading to do to increase your familiarity with cluster / managed servers.
How to setup servers so that I can start them automatically from administration console?Add the 3 servers into your cluster. Use the cluster to start and stop all 3 servers from within the console instead of starting / stopping each server individually.
How to configure address in administration console through which I will open my application in a browser?You'll need some sort of load balancer to direct traffic so that the end user doesn't have to know the server/port combinations. Apache + Weblogic plugin for instance, but I don't think you'll be keeping all 3 instances on the same physical machine as your production design.
And after that, how to configure that when server on which I work breaks, it automatically restarts application in another server (no need for failover because BI Publisher does not support session replication, I think)?Target your application to "All servers in the cluster". You should have your managed instances on separate physical machines since your current configuration is vulnerable to a single machine failure which would shutdown all 3 instances.

Usb print servers?

Hello, I have a question on usb print servers. I got the D-Link DPR-1260 wireless print server but couldn't get it working even after calling tech support and being on with them for several hours. Also, they had me trying to set it up through XP on my intel laptop which I didn't like. I have a G5 tower non intel and an intel laptop. I want to connect to my printers which is a brother HL-5250DN and an epson r300. The Printers are not close to my desktop for space reasons and the only way I can connect to them right now is by placing my laptop next to them and connecting through the usb.
I was wondering if anyone knows of a good wireless(preferable) or wired usb 4 port hub that I can get that is very compatible with my macs as well as PC's. I thought the D-Link DPR-1260 was it but was disappointing.
Thanks.

Jdvb,
> one of my LPT printers stopped working, and well, USB printers are more
> available.
> How do I get a USB printserver to service my NetWare 6.5 queue.
>
> I have ordered a D-link DPR-1061 printserver, though I am unsure of how
> to set it up in Nwadmin or something similar.
> My suplier stopped support for NetWare and I am basically clueless of
> how to work with NetWare.
>
> The Novell Netware printer works primarilly on IPX.
>
> I am unsure of how to make it work, the printserver also supports
> unix/Appletalk which I also see as options in Nwadmin when I add a
> printer.
> Though when I load Pserver and then the printserver it fails to load
> the driver for either appletalk/unix.
>
> please help
> Please help.
You need to install and configure NDPS (iPrint). The procedure is covered
in the docs and queue-based and NDPS can coexist. You then create a
printer in NDPS, have it service the queue. For output you use ypur
printer, configured as LPR.
- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)
Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

Wirless Print Servers with Mac and Windows

I am very new to mac..macbook purchased just this week..facing some challenges but learning at the same time..I have my macbook running thru my wireless network on a Motorola SB4100 Cable modem, D-Link DI 614+ Wirless Broadband router and a d-link DPR-1260 Wirless Print Server..previously I have been using a Windows Laptop..I guess it seems that D-Link print servers are only for Windows systems??? I looked at the manual and it doesn't mention Mac..haven't been able to figure out how to add a prt to the mac and I guess that is why?...you need a seperate print for the mac with it's own wirless prt server? or can you replace the cable modem and router with some apple base station that does everything but then can windows laptop work on the network and wireless prt??
scott

I doubt you need any additional equipment. It should be a matter of setting up using PrinterBut posting your question in the Tiger- Printing & Faxing forum area may get you a faster answer.
http://discussions.apple.com/forum.jspa?forumID=756
It should be a matter of setting up in Printer Setup Utility using the ip address of the server.

CSS 11503 load-balancing with MS Print Servers

We are trying to load-balance print server connections between 2 MS print servers. When we try to connect to the print servers name, (\\PS01) or even the VIP address, we get a Path not found error. However, if we direct the path to the actual name or ip address of the print servers (not the VIP), we can view all the queues and connect/print to them. Is this possible to do on the CSS 11503? Thanks.

Pete- Here is our config. See any problems?
configure
!*************************** GLOBAL ***************************
ip route 0.0.0.0 0.0.0.0 1.100.100.100 1
!************************* INTERFACE *************************
interface 1/2
bridge vlan 2
!************************** CIRCUIT **************************
circuit VLAN1
ip address 1.100.101.110 255.0.0.0
circuit VLAN2
ip address 10.100.249.1 255.255.255.0
!************************** SERVICE **************************
service ps01
ip address 10.100.249.5
active
service ps02
ip address 10.100.249.6
active
!*************************** OWNER ***************************
owner printserver
content L3_Basic
add service ps01
add service ps02
vip address 1.100.100.35

Print servers and printers problems on Win7 and Win8

Hello,
We have some computers, working on Windows operating system in the office: a few forking on the good old XP sp3, one running on the Win7 x64 home edition and one running on Win8 professional (the last one installed for new OS testing purposes)
During last two months I have tested a few print servers attempting to find one which can work with Windows 7: Trendnet, Synology, and D-link print servers. However, unsuccessfully. Here is the result:
   1) Any print servers is working perfectly with WinXP sp3 (full printing and MFP function support, easy configuration and access, successfully scanning and printing operations in 100% cases)
   2) No one print server is working correctly with Win7 home x64 (mostly successful installation but complicated and unclear configuration; printed pages often is missing, no scan support for MFP.
   3) There is a little bit better situation with Win8: 100% printing support on the same equipment but no scan support for MFP
Could you please help me with followings:
1) Could you please help me configure print servers and printers on Win7 x64, including printing and scanning support?
2) Could you please help me configure scanning support for Win8?
Please find full list of affected hardware bellow:
1) Machines, running on Win XP: Panasonic CF-29, CF-74, HP Compaq dc7600, some Acer laptops;
2) Machine, running on Win7 x64 home: Asus UX21, (OS probably was preinstalled on the factory)
3) Machine, running on Win8 pro: Lenovo X200 tablet
4) Printer HP LJ1020 with drivers for XP and Win7, x86 and x64
5) MFP printer Canon MP600 with drivers for XP and Win7, x86 and x64
6) Print server: D-link DPR-2000
7) Router: Cisco RV042G
All the machines has correct drivers installed, all the printers supports all the services if connected to computer directly. I have made all possible steps solving mentioned problems, including automated problem solving wizards on Win7.
Thanks in advance for your support

Hi,
Regarding the printer configure issue, I would like to share the following article:
Managing Printers and Print Servers
http://technet.microsoft.com/en-us/library/cc754769.aspx
According to the scanning support for Win8, it is better to post this issue in Windows 8 forum for more help.
Regards,
Vincent Wang
TechNet Community Support

Epson Print Servers compatible with Time Capsule?

First up: I'm no techie. Epson tells me I will need an Epson print server to enable me to print wirelessly on my ADSL-Time Capsule 500GB (7.3.2)-Airport (5.3.2) network, using an Epson DX8400, which they tell me doesn't support network printing: so far so bad (& so much for the cheap all-in-one printer). Can anyone tell me (if there is no other way of achieving wireless printing) if the Epson print servers are compatible with Time Capsule? I don't have the tech spec to hand, but there are only 3 PSs on the Epson website, 2 of which appear to be the same but vary by a few pounds in price (about GBP150). This was an expense I didn't want, but if I can print wirelessly (AND IT WORKS!) I will pay it, because I want to get a desktop model as well soon & will want to print wirelessly from that as well. I have posted this to the Time Capsule forum as well, but any help gratefully received. Thanks in advance.

yep am using a usb hub,time cap. has only the one usb port- yes two usb outs on the hard drive , sorry, which merge into one into the hd, is bus powered...

Print Servers Impact after unicode conversion

Hi
We are performing an CUUC from 4.6C to ECC 6.0
Our customer has around 4-5 windows special print servers which are used for chinese, japanese, korean printing..etc.
After the upgrade & unicode conversion
- Do we still need to use all these 4-5 special print servers for each languages seperatly? or
- We shall consolidate all these print servers into one print server? Or
- We don't need to have any print servers, all the print queues can be pointed to unix print queues and then to the printers directly.
Kindly advise
Thanks & Regards
Senthil

I would think you could consolidate the print servers, but you still need the separate printers/device types in SAP. We use a single print server for EN/DE/ZH but have different SAP printers (usinging different device types) for EN/DE & ZH printers.

Joy of Print Servers; USB success

I administer a Netware 4.11+sp9 network, small by most standards. We
also have Internet capability, using a commodity-quality Linksys router
as a DHCP server, for most IP addresses. Our Netware server, however,
runs IPX exclusively.
I have read some of Peter Kuo's advisories that extol the virtues of lpr
(unix) printing, methods I have scarcely ever employed for any Netware
purposes. I suppose there is virtue in that, for interfacing to USB
printers. It's a point I should investigate.
However, I prefer to use "external print servers." I have done so for
years, satisfying the needs of both Netware printing and Windows
printing. This was always done by connecting said print servers to the
PARALLEL ports of various laser printers.
Meanwhile, I have long avoided the tactic of sharing printers attached
to workstations. I want my printers to work without that crutch.
My print server strategy has been threatened, however, by the
disappearance of parallel-printer-port-equipped printers from the
marketplace. USB is everywhere, at low cost. (Integrated internal
print servers are declined for cost reasons.)
I have used convenient, small StarTech.com print servers, which have
attached directly to the parallel connector inside the case of an HP 6
Laser printer; that's how small those print servers are. But the best
thing about this item is the software; PS Admin has worked reliably and
easily, unlike software I've used to get earlier Netware-compatible
external print servers to work. (Linksys had a bad example in its
EFSP42 print server.)
So I was delighted to happen upon a USB2.0-compatible print server,
available at NewEgg.com for less than $50USD, that used PS Admin for
configuration purposes. I installed the print server, connecting it to
my old NEC1400 Superscript printer, which probably only complies with
the early USB standard. It all works, both for Netware and Windows
printing.
For the first time, I have actually printed a conventional Netware print
job to a USB printer. This worked, despite the absence of provision in
NDS administration to configure the "printer" for USB. In fact, said
"configuration" seems to have been completely ignored, fortunately.
I am using conventional queue-based printing. PS Admin made it easy. I
even got to use my own names, for devices, queues, etc. And those same
names showed up in my NDS tree, upon later inspection.
I don't have the invoice in front of me right now, which reveals the
make and model of this print server. I'll post that later, when I
return to my business office.
Hopefully, this "USB success story" will help some other Netware
enthusiasts.

Thanks for this definitive answer.
Given Vista's antipathy for IPX, a sense of finiteness..., ensues.
Assuming there is a "desire" for Vista, is an upgrade from Netware 4.11+sp9
to 5, or 6, a remedy? I recall that 5 is "IP only."
Needless to say, if the existing system has *applications* that require IPX,
then we cannot dispense with this protocol, unless we replace those
applications. So, for this hypothetical case, let us assume no such
IPX-dependent applications exist.
Does queue-based printing still work in 5? I don't manage a large enough
network to justify NDPS.
Sent via OE by John, from MERCURY
"Barry Schnur" <[email protected]> wrote in message
news:[email protected]..
> John, you emailed me with this (please lets keep this here in the
> newsgroups)
>
>
> >>Thank you for this astute warning.
>
> >>Isn't IPX optional with 4.11+sp9?
>
> >>I mean, one might say that IP is optional, but then again, if IP can
> >>do everything (That's a big IF...) that IPX can do, then I should be
> >>able to dispense with IPX and SPX, altogether.
>
> The answer here is no -- that is, you need *native* IP (Netware 5.0 and
> up), which you *can't* get in NW 4.11/4.2. So with all prior versions
> (4.2 and less), you must have IPX. With Vista, there is no IPX stack
> to work with (Novell has used the Microsoft OS stacks with Windows NT
> and up).
>
>
> --
> Barry Schnur
> Novell Support Connection Volunteer Sysop

Windows Server 2012 - Printing using UNC path not working

Hi,
I have a problem printing using the printer's UNC path ("\\Server_Name\Printer_Hostname") to work with a web
app hosted on IIS 8. With a windows forms application the UNC path is working fine and the app prints.
With
the web app I receive an error "The data area passed to a system call is tool small".
Also,
in the event viewer under Applications and Services Logs -> Microsoft -> PrintService -> Operational, I receive the error "The print spooler failed to reopen an existing printer connection because it could not read the configuration information
from the registry key S-1-5-82-1980832875-2702362896-1795126167-3622310632-1152289074\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable."

I have contacted IIS forum support.
Please review the link: http://forums.iis.net/p/1213109/2079229.aspx?Re+Windows+Server+2012+Printing+using+UNC+path+not+working
Their final response:
Printing from ASP.NET using System.Drawing.Printing itself is a horrible approach, as this namespace was designed for Windows Forms only. The designers did not take everything about ASP.NET in mind, so any issue can happen. That can answer why the HP model
works while the Samsung fails, as the HP one just "happens
to work",
http://msdn.microsoft.com/en-us/library/system.drawing.printing.printdocument.aspx
Similarly, System.Printing was designed just for WPF.
About which printing API to use in ASP.NET/IIS, there is no clear answer so far. Thus, your only resource is Microsoft support, who can perform further analysis (with their dedicate utilities and of course Windows source code) and might come across a solution
to help you out. This is not a trivial scenario.

NLB or Cluster 2012 Print servers

Similar Messages

Maybe you are looking for