Agent Windows installation without administrator role

Hi,
due to security, I have to install 10.2 agent with a specific OS user that cannot be part of "Administrators" group.
Which are the "rights" I need to ask to OS admin to successfully install and use the agents?
Thanks
mike

Refer the doc
http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/installing_agent.htm#insertedID1
for Microsoft Windows) Ensure that the agent user account has permissions and rights to perform the following:
Act as part of the operating system.
Increase quotas.
Replace process level token.
Log in as a batch job.
To verify whether the agent user has these rights, follow these steps:
1.
Launch the Local Security Settings.
From the Start menu, click Settings and then select Control Panel. From the Control Panel window, select Administrative Tools, and from the Administrative Tools window, select Local Security Settings.
2.
In the Local Security Settings window, from the tree structure, expand Local Policies, and then expand User Rights Assignment

Similar Messages

  • Installation without Administrator Privileges

    Hi All
    From what I can gather from AIR documentation, one cannot install or update AIR, or install or update AIR applications without administrator privileges.
    We roll out applications to hundreds of medium size businesses (dealerships) and this represents a huge problem as most employees at these companies do not have admin rights.  None of these sites has automated network installs, and all have different situations regarding IT support.
    Our current desktop application requires no admin privileges and introducing the AIR portion of our product has caused a big snag.
    Is there any way to get around this?  Are future versions going to support some way of doing this?
    We would probably be ok if we had to do one administrator install of AIR and the app,  if further application updates did not require admin rights.
    Thanks
    Ken

    Exactly. A feature that allows Enterprise IT to "bless" an AIR application would be great. The AIR Update Framework is such a great feature. I hate the fact that I cannot use it on my largest AIR installations. That means more expense for us, and our desktop engineering jobs are safe...
    From my understanding, the AIR Update Framework already ensures that the digital certificate in an update matches the digital certificate of the installed app. This guarantees that the update came from the same trusted publisher of the app. Very nice.
    I think I also read somewhere that on Windows, AIR apps are always installed in the "All Users" profile -- both file system and Registry. An option to install an AIR app in a user's profile would also work for us, if that helps.
    So even if we have to SMS the initial application install (with our production digital certificate), allowing the app to update itself would save us a lot of time, effort, money, headaches, etc...

  • Portal Installation : User Administration -- Role workset error

    Dear All,
    We have installed EP NW04 SR1 . Every thing is working fine, All the menus are coming up properly except when i click on the User Administration --> Role --> Role menu, its starts for some time and then gives "Page cannot be displayed, Operation aborted" . This error only comes for the Role workset. Every thing else is working fine.
    It would be nice if i can get guidance as to how to debug this error
    Regard
    PN

    Hi,
    I am still unable to solve the problem. The same problem persists with the ROLE and User Mapping.
    I try to open it and it gives the "page cannot be displayed, operation aborted " error
    Help is appreciated
    Regards
    PN

  • Deleting print drivers on Windows Server 2008 R2 without Print Role

    Hi,
    I'm using Windows Server 2008 R2 with Citrix Xenapp for published desktops meaning that i need to add a number of different printers to the server for the various users. Unfortunately i have some printer drivers that i think are conflicting and want to remove
    these from the server.
    How can i do this without adding the Print and Document Services role? Without this role i don't believe i can access 'Print Management' in the same way that i would with a Windows 7 client and then remove the driver package.
    Is there another way that i can do this or should i be adding this role just to remove these drivers and then perhaps removing the role (if necessary), assuming that this is possible?
    Thanks for any help.

    add the tools for print management
    in elevated cmd window
    dism /online /enable-feature /featurename:Printing-AdminTools-Collection
    If you already have local shared prints on the server, add the role.  Adding the Role installs the tools and opens the File and print sharing firewall port which would have been achieved by adding a shared printer. You do not need to add the Print
    role to setup a machine as a print server, it's not a requirement. 
    Alan Morris Windows Printing Team

  • Upgrade to version 10.5.x, error - "There is a problem with the Windows Installer Package". I'm installing as Administrator, and have done an uninstall of the earlier version. Any ideas??

    Hi; Attempting to upgrade to version 10.5.x, but I keep on getting an error - "There is a problem with the Windows Installer Package". I'm installing as Administrator, and have done an uninstall of the earlier version. Any ideas??
    Needing to upgrade to allow connection of a 4S iPhone to the Laptop.
    Thanks!! - Tim.

    Repair your Apple Software Update.
    Go to START/ALL PROGRAMS/Apple Software Update. If it offers you a newer version of Apple Software Update, do it but Deselect any other software offered at the same time. Once done, try another iTunes install
    If you can't find ASU in all program, you can do it in CONTROL PANEL, ADD N REMOVE PROGRAMS.

  • No access to new default desktop without Super Administrator role

    I have created new desktops and rule collections. All new rule collections are linked to in the master rule collection under folder 'Super adminstrators'.
    Now when I try to log on as a normal user his new desktop is not displayed - instead an error message saying that he doesn't have access appears.
    If I assign the user the Super Administrator role, then the correct new desktop is displayed.
    What setting am I missing?
    Henning Strand

    Hi,
    To fix the problem with the Portal Desktop, make sure that all users that it is assigned to have permissions to it and to every folder in the path to it (including the "End User" checkbox checked).
    Check this:
    Error accessing default desktop for a user
    Regards,
    Praveen Gudapati

  • [Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

    As we all know,
    the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
    Essentials Experience role in Server Manager or via Windows PowerShell.
    In this article, we introduce the steps to install and configure Windows
    Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
    Before installing the Windows Server Essentials Experience Role, please use
    Get-WindowsFeature
    PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
    Figure 1.
    Part 1: Install Windows Server Essentials Experience role locally
    Add Windows Server Essentials Experience role
    Run Windows PowerShell as administrator, then type
    Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
    Figure 2.
    Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
    (Figure 3)
    Figure 3.
      2. Configure Windows Server Essentials Experience role
    (1)  In an existing domain environment
    Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
    Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
    Figure 4.
    After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
    Server Essentials:
    Start-WssConfigurationService –Credential <Your Credential>
    Note: The type of
    Your Credential should be as: Domain-Name\Domain-User-Account.
    You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
    Figure 5.
    Next, you can type the password for the domain account. (Figure 6)
    Figure 6.
    After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
    Figure 7.
    By the way, you can use
    Get-WssConfigurationStatus
    PowerShell cmdlet to
    get the status of the configuration of Windows Server Essentials. Specify the
    ShowProgress parameter to view a progress indicator. (Figure 8)
    Figure 8.
    (2) In a non-domain environment
    Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
    Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
    Figure 9.
    After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
    After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
    After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
    Figure 12.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Part 2: Install and configure Windows Server Essentials Experience role remotely
    In an existing domain environment
    In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
    Add-WindowsFeature -Name ServerEssentialsRole
    -ComputerName xxx -Credential DomainName\DomainAccount
    Figure 13.
    After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
    Figure 14.
    After the installation completes, it will return the result as below:
    Figure 15.
    Next, please use the
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
    Enter-PSSession –ComputerName
    xxx –Credential DomainName\DomainAccount (Figure 16)
    Figure 16.
    Then, please configure Server Essentials Role via
    Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
    Figure 17.
    After your credential is accepted, it will update and prepare your server. (Figure 18)
    Figure 18.
    After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
    Figure 19.
    2. In a non-domain environment
    In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
    below:
    Sevrer1: 192.168.1.54
    Server2: 192.168.1.53
    Run
    Enable-PSRemoting –Force on Server1. (Figure 20)
    Figure 20.
    Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
    to
    add the TrustedHosts entry:
    Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
    (Figure 21)
    Figure 21.
    Next, we can use
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
    Figure 22.
    After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
    Figure 23.
    From figure 24, we can see that the installation is completed.
    Figure 24.
    Then you can use
    Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
    The figure below shows the status of Windows Server Essentials.
    Figure
    25.
    Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
    Figure 26.
    More information:
    [Forum
    FAQ] Introduce Windows Powershell Remoting
    Windows Server Essentials Setup Cmdlets
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

  • Premier Elements 11 Windows installer problems

    I am having a problem installing Premier Elements 11on my Windows 8 (64 bit) Laptop. I purchased the Elements Combo pack and when I install Photoshop Elements it works flawlessly. However, when I attemp to install Premier Elements it asks me to choose my installation language then I get an unusual Windows Installer screen and it will not let me advance any further.
    This is the Windows Installer screen that pops up after it tries to configure the installation process:
    Windows ® Installer. V 5.0.9200.16384
    msiexec /Option <Required Parameter> [Optional Parameter]
    Install Options
    </package | /i> <Product.msi>
      Installs or configures a product
    /a <Product.msi>
      Administrative install - Installs a product on the network
    /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
      Advertises a product - m to all users, u to current user
    </uninstall | /x> <Product.msi | ProductCode>
      Uninstalls the product
    Display Options
    /quiet
      Quiet mode, no user interaction
    /passive
      Unattended mode - progress bar only
    /q[n|b|r|f]
      Sets user interface level
      n - No UI
      b - Basic UI
      r - Reduced UI
      f - Full UI (default)
    /help
      Help information
    Restart Options
    /norestart
      Do not restart after the installation is complete
    /promptrestart
      Prompts the user for restart if necessary
    /forcerestart
      Always restart the computer after installation
    Logging Options
    /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
      i - Status messages
      w - Nonfatal warnings
      e - All error messages
      a - Start up of actions
      r - Action-specific records
      u - User requests
      c - Initial UI parameters
      m - Out-of-memory or fatal exit information
      o - Out-of-disk-space messages
      p - Terminal properties
      v - Verbose output
      x - Extra debugging information
      + - Append to existing log file
      ! - Flush each line to the log
      * - Log all information, except for v and x options
    /log <LogFile>
      Equivalent of /l* <LogFile>
    Update Options
    /update <Update1.msp>[;Update2.msp]
      Applies update(s)
    /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
      Remove update(s) for a product
    Repair Options
    /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
      Repairs a product
      p - only if file is missing
      o - if file is missing or an older version is installed (default)
      e - if file is missing or an equal or older version is installed
      d - if file is missing or a different version is installed
      c - if file is missing or checksum does not match the calculated value
      a - forces all files to be reinstalled
      u - all required user-specific registry entries (default)
      m - all required computer-specific registry entries (default)
      s - all existing shortcuts (default)
      v - runs from source and recaches local package
    Setting Public Properties
    [PROPERTY=PropertyValue]
    Consult the Windows ® Installer SDK for additional documentation on the
    command line syntax.
    Copyright © Microsoft Corporation. All rights reserved.
    Portions of this software are based in part on the work of the Independent JPEG Group.
    Have there been any reports of a faulty installer with Premier in the Boxed set? Photoshop installed so seamlessly it's odd that this is popping up.
    Thanks in advance!!

    Eitehr your Windows installer is damaged or you run without sufficient user privileges. Run Windows Update to repair the installer and make sure to run as admin. also turn off any security stuff temporarily.
    Mylenium

  • How to get Zen Touch to work on Windows Vista without PFS (worked!)

    CHow to get Zen Touch to work on Windows Vista without PFS (worked!)? ***THIS WORKED***
    For all of you that want to get their music out of the Zen touch, and are stuck with Vista and .0.03 firmware (non vista recognisable), and don't want to erase everything by installing the latest firmware, here is what worked for me:
    )Uninstall every piece of Touch software you got and reboot.
    2) Download the latest drivers from Creative: JB3MV2...exe, together with the latest Nomad explorer, and the latest Notmad explorer from Red Chair (a trial is enough, version 9.0.3 currently).
    3) Right click the driver, properties, go to compatibility mode, and select Windows XP SP2. Make sure your Zen is unplugged (worked for me that way). Right click the driver installer again and Run as Administrator. It hanged around 72% for me, no biggy, open your task manager and shut the installer off.
    4)Before rebooting, install Notmad explorer.(I installed only the Zen touch part of it. I tried to run it right away but got a 'cannot find explorer.exe error - again, no biggy).
    5) Reboot, plug in your Zen. Again for me, Notmad didn't work. This is what worked: Without messing up anything, install Nomad Explorer by Creative on top of it all, and reboot again.
    6) After reboot, with your Zen still plugged in, right click the little Notmad icon on the right part of the taskbar and select 'Connect Jukebox Zen'. And voila, check your explorer, it should hopefully recognise the Zen Touch like windows xp would.
    If you still run into trouble, just install stuff from the beggining, making sure Compatibility: WinXP SP2 and Run as Admin are used everywhere, and keep rebooting till it hopefully works.
    Best of luck. edit: Using Winamp to transfer files worked as well.

    Hi D2xS-Shooter,
    I am afraid Creative Cloud desktop app is not compatible with Windows Vista. If you run into problems there are very limited resources from Adobe to assist.
    Creative Cloud is a collection of apps with various different tech specs
    http://www.adobe.com/uk/products/creativecloud/tech-specs.html
    Thanks!
    Eshant

  • Deploying msi via group policy without administrative rights

    We are having a problem with flash player not working without
    Administrative right on the machine. We thought we could get around
    this by using the flash_player_active_x.msi and installing through
    group policy. The install during a computer reboot (if assigning to
    a computer) or during a user sign on (if assigned to a user) seems
    to work fine.
    However, when you actually try to load a webpage with flash,
    nothing. The component doesn't actually get installed into the
    browser. As soon as you log on with a privilaged account, and
    browse to a flash enabled page, the install finishes, the active x
    control is loaded and now all users can see it.
    However, I'd really prefer not to have to go around to each
    computer and log on with the administrator account - kind of
    defeats the purpose of group policy.
    All computers are Win XP sp2 with IE 7. The active directory
    server is a Win2k server.
    Any thoughts would be appreciated.

    I am having this issue also. Has anyone found a solution?
    I found this reference on this website, but there is no
    solution given:
    I
    have installed Adobe Flash Player but still don't see any Flash
    content. What is wrong?
    quote:
    Restricted User accounts are unable to display Flash Player
    content
    After successful installation under the Windows Administrator
    account, Restricted User accounts are unable to display Flash
    Player content. This issue has been reported on Microsoft Windows
    XP Service Pack 2 systems and occurs sporadically. It may also
    affect other versions of Windows, such as Windows 2000.
    If you installed Flash Player 8.0.24.0 prior to April 6,
    2006, then you must remove it using the Flash Player uninstaller
    released on May 11, 2006. Remove Flash Player using the
    instructions in How to uninstall the Adobe Flash Player (TechNote
    14157).

  • Windows 2008 r2 windows installer issue error 1719 when install Backup exec 12.5

    Hi all
    After a epic weekend of rebuilding our exchange server I have tried to reinstall Backup exec 12.5 64bit, this was installed with no issues during the last build, however at the end of this build I went to reinstall Backup Exec 12.5 and it is failing with
    error 1719 Windows installer issue.
    I have looked on many sites and tried many things non of them have worked, has anyone managed to resolve this issue.
    Dave
    DJH

    Hi Lenora
    See below
    Symantec Backup Exec (TM) 12.5 for Windows Servers Installation Log
    03-19-2013,17:33:38 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\setup.exe
    03-19-2013,17:33:38 : CSetupApp::GetInstalledGUID
    03-19-2013,17:33:38 : CSetupApp::LoadSetupXML
    03-19-2013,17:33:38 : CSetupApp::ScanXML
    03-19-2013,17:33:38 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\Bin\Setup.xml
    03-19-2013,17:33:38 : MSI File Name = WindowsInstaller-KB893803-v2-x86.exe
    03-19-2013,17:33:38 : MSI Version = 3.1
    03-19-2013,17:33:38 : MSI Package Name = Symantec Backup Exec for Windows Servers.msi
    03-19-2013,17:33:38 : System Central Processor = 64
    03-19-2013,17:33:38 : Product Type = SETUP_BEX64
    03-19-2013,17:33:38 : Product Name = Symantec Backup Exec for Windows Servers
    03-19-2013,17:33:38 : Current Installing GUID ={BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:33:38 : Product Version = 12.5
    03-19-2013,17:33:38 : CSetupSupport::IsValidMSIPackage
    03-19-2013,17:33:38 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\Symantec Backup Exec for Windows Servers.msi
    03-19-2013,17:33:38 : {BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:33:38 : {BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:33:38 : Equal PID
    03-19-2013,17:33:38 : Product version: 12.5.2213
    03-19-2013,17:33:38 : StartBESequence
    03-19-2013,17:33:38 : Executing BE_PreCheckInstall
    03-19-2013,17:33:38 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:33:38 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:33:38 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,17:33:38 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,17:33:38 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:33:38 : Executing StartBESequence
    03-19-2013,17:33:38 : Pulling user data from the MSI
    03-19-2013,17:33:38 : Upgrade state set to 0
    03-19-2013,17:33:38 : Executing SSO::PullDataMSI()
    03-19-2013,17:33:38 : Executing CDlgCAS::PullDataMSI()
    03-19-2013,17:33:38 : MSI processing complete
    03-19-2013,17:33:38 : Pulling user data from the command line
    03-19-2013,17:33:38 : COMMAND LINE: Checking UIMODE value
    03-19-2013,17:33:38 : COMMAND LINE: Checking for program group placement value
    03-19-2013,17:33:38 : COMMAND LINE: Checking for main feature selection
    03-19-2013,17:33:38 : COMMAND LINE: Checking for serialization values
    03-19-2013,17:33:38 : CDlgChooseCustom::PullDataSilent
    03-19-2013,17:33:38 : After check for parameter file exists.
    03-19-2013,17:33:38 : CDlgLocalChooseCustom::Pass
    03-19-2013,17:33:38 : After Check for INSTALL_CHOICE.
    03-19-2013,17:33:38 : After Check for INSTALL_TYPE.
    03-19-2013,17:33:38 : After Check for INSTALL_MODE.
    03-19-2013,17:33:38 : CDlgLocalChooseCustom Pass Function end.
    03-19-2013,17:33:38 : Agent for Microsoft Exchange Server was added for evaluation
    03-19-2013,17:33:38 : Agent for Microsoft SQL Server was added for evaluation
    03-19-2013,17:33:38 : Ignoring the TSM switch.
    03-19-2013,17:33:38 : COMMAND LINE: Checking for service account values
    03-19-2013,17:33:38 : Not in Maintenance mode
    03-19-2013,17:33:38 : Getting the Silent Params.
    03-19-2013,17:33:38 : COMMAND LINE: checking for SSO values
    03-19-2013,17:33:38 : COMMAND LINE: checking for DlgChooseDBServer values
    03-19-2013,17:33:38 : COMMAND LINE: Checking for tape drivers values
    03-19-2013,17:33:38 : COMMAND LINE: Checking for TSM values
    03-19-2013,17:33:38 : COMMAND LINE: checking for CASO values
    03-19-2013,17:33:38 : COMMAND LINE: Checking for clone values
    03-19-2013,17:33:38 : COMMAND LINE: Checking progress settings
    03-19-2013,17:33:38 : COMMAND LINE: Checking for NOINSTALL value
    03-19-2013,17:33:38 : Setup Command Line = "D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\setup.exe"
    03-19-2013,17:33:38 : List of switches set follows:
    03-19-2013,17:33:38 : /DEST: = C:\Program Files\Symantec1\Backup Exec\
    03-19-2013,17:33:38 : /SNO: = 0930292112010690
    03-19-2013,17:33:38 : /USER: = backup
    03-19-2013,17:33:38 : /DOM: = ACCENTPRESS
    03-19-2013,17:33:38 : /PASS: = ********
    03-19-2013,17:33:38 : /TS:
    03-19-2013,17:33:38 : /TD: = ALL
    03-19-2013,17:33:38 : /DOCS:
    03-19-2013,17:33:38 : /LOADER:
    03-19-2013,17:33:38 : /AOFO:
    03-19-2013,17:33:38 : /EXCH:
    03-19-2013,17:33:38 : /SQL:
    03-19-2013,17:33:38 : /NTA:
    03-19-2013,17:33:38 : /RAULUS:
    03-19-2013,17:33:38 : /DBSERVER:
    03-19-2013,17:33:38 : /DBINSTPATH: = C:\Program Files\Microsoft SQL Server\BE\
    03-19-2013,17:33:38 : /BACKUPDATA: = 0
    03-19-2013,17:33:38 : /MAC:
    03-19-2013,17:33:38 : Command line processing complete
    03-19-2013,17:33:38 : Install set to run in UI mode
    03-19-2013,17:33:38 : CDlgPushWelcome::Pass
    03-19-2013,17:33:40 : CinstOpenDlg::ValidateData
    03-19-2013,17:33:43 : Validating license data
    03-19-2013,17:33:44 : CDlgChooseInstall::ValidateData
    03-19-2013,17:33:44 : CDlgValidationSummary::LaunchValidationTest
    03-19-2013,17:33:44 : m_bUseNativeClient = 1
    03-19-2013,17:33:44 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:33:44 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:33:44 : Connected to SQL Server.
    03-19-2013,17:33:44 : m_bUseNativeClient = 1
    03-19-2013,17:34:05 : CDlgValidationSummary::ValidateData
    03-19-2013,17:34:05 : BEOperations::BE_GetInstalledProdCodeVersion
    03-19-2013,17:34:05 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:34:05 : CDlgSerialNumber Pass Function.
    03-19-2013,17:34:05 : After Check for Remote_Install.
    03-19-2013,17:34:05 : After Check for RA_INSTALL.
    03-19-2013,17:34:07 : Validating serialization data
    03-19-2013,17:34:07 : CDlgLocalChooseCustom::Pass
    03-19-2013,17:34:07 : After Check for INSTALL_CHOICE.
    03-19-2013,17:34:07 : After Check for INSTALL_TYPE.
    03-19-2013,17:34:07 : After Check for INSTALL_MODE.
    03-19-2013,17:34:07 : CDlgLocalChooseCustom Pass Function end.
    03-19-2013,17:34:07 : On Init of CDlgChooseCustom
    03-19-2013,17:34:07 : Leaving Init of CDlgChooseCustom
    03-19-2013,17:34:07 : CDlgLocalChooseCustom::OnInitDialog
    03-19-2013,17:34:07 : On Init of CDlgLocalChooseCustom
    03-19-2013,17:34:07 : Leaving Init of CDlgLocalChooseCustom
    03-19-2013,17:34:12 : Validating Local Options Data
    03-19-2013,17:34:13 : Validating service account data
    03-19-2013,17:34:13 : CDlgSSO Pass Function.
    03-19-2013,17:34:13 : After Check for INSTALL_MODE.
    03-19-2013,17:34:13 : DlgChooseDBServer Pass Function.
    03-19-2013,17:34:20 : m_bUseNativeClient = 1
    03-19-2013,17:34:20 : Validating DlgChooseDBServer data
    03-19-2013,17:34:20 : Drive C:     Required: 1102 MB     Available: 37138 MB
    03-19-2013,17:34:20 : CDlgChooseTapeDrivers Pass Function.
    03-19-2013,17:34:20 : After Check for INSTALL_MODE.
    03-19-2013,17:34:20 : After Check for INSTALL_CHOICE.
    03-19-2013,17:34:20 : After Check for INSTALL_TYPE.
    03-19-2013,17:34:20 : CDlgSerialNumber Pass Function.
    03-19-2013,17:34:20 : CDlgCAS Pass Function.
    03-19-2013,17:34:20 : After Check for INSTALL_MODE.
    03-19-2013,17:34:20 : CDlgClone Pass Function.
    03-19-2013,17:34:20 : CDlgClone not passed.
    03-19-2013,17:34:20 : CDlgRemoteChooseCustom Pass Function.
    03-19-2013,17:34:20 : After Check for INSTALL_CHOICE.
    03-19-2013,17:34:20 : Install Summary XML File:
    03-19-2013,17:34:20 : C:\Users\ADMINI~1\AppData\Local\Temp\1\BE61998B-E5BD-4E41-B2D7-96551E6FECE0\InstallReview.xml
    03-19-2013,17:34:20 : Install Summary XSL File:
    03-19-2013,17:34:20 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\Bin\InstallSummary.xsl
    03-19-2013,17:34:20 : Install Summary HTML File:
    03-19-2013,17:34:20 : C:\Users\ADMINI~1\AppData\Local\Temp\1\BE61998B-E5BD-4E41-B2D7-96551E6FECE0\InstallReview.htm
    03-19-2013,17:34:20 : Not Quickstart Edition
    03-19-2013,17:34:20 : Entering GetSQLAndCASOInformation
    03-19-2013,17:34:20 : Leaving GetSQLAndCASOInformation
    03-19-2013,17:34:20 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:34:20 : m_bUseNativeClient = 1
    03-19-2013,17:34:20 : *************** About Backing Up Exchange 2007 Servers *************** To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this
    computer.  The Management Tools can be installed during a custom install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft
    Exchange Server MAPI Client and Collaboration Data Objects package version 06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,17:34:21 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:34:27 : Executing InstallLiveUpdate.
    03-19-2013,17:34:40 : Installing .Net Framework 2.0 SP1.
    03-19-2013,17:34:40 : Checking for .Net Framework 2.0 SP1.
    03-19-2013,17:34:40 : Vista or Longhorn server.  Not installing .NET Frameworks.
    03-19-2013,17:34:40 : .NET Framework was detected.  Skipping install.
    03-19-2013,17:34:41 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,17:34:41 : m_bUseNativeClient = 1
    03-19-2013,17:34:41 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes;DATABASE=master
    03-19-2013,17:34:41 : SQL Server version 9
    03-19-2013,17:34:41 : SQL version returned:  9
    03-19-2013,17:34:41 : Executing SQL_GetServicePack.
    03-19-2013,17:34:41 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:34:41 : Connected to SQL Server.
    03-19-2013,17:34:41 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:34:41 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:34:41 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:34:41 : Connected to SQL Server.
    03-19-2013,17:34:41 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Express Edition
    03-19-2013,17:34:41 : "D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\SQLExpress\SQLEXPR.exe" /wait /qn /norestart /lv "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt" INSTANCENAME=BKUPEXEC SQLACCOUNT="NT AUTHORITY\SYSTEM" SQLPASSWORD=""
    UPGRADE=SQL_Engine,SQL_Data_Files,SQL_Replication,Client_Components,Connectivity SAPWD=**** DISABLENETWORKPROTOCOLS=0
    03-19-2013,17:34:45 : V-225-53:  ERROR: Failed to install SQL Express BKUPEXEC instance with error 1601.  ***To search for information about this error, click
    here
    03-19-2013,17:34:45 : Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.
    03-19-2013,17:34:45 : Failed to install third party products.
    03-19-2013,17:37:25 : Validating install complete
    03-19-2013,17:37:25 : Success unloading BEINSTDLGS.DLL.
    03-19-2013,17:37:25 : CLEANUP: Install has removed the following files from: C:\Users\ADMINI~1\AppData\Local\Temp\1\{BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:37:25 : Removed files:
    03-19-2013,17:37:25 : ERROR:  Installation failed with error 1603.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,17:41:16 : Windows Operating System Version: 6.1
    03-19-2013,17:41:16 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,17:41:18 : Executing managed _Setup:
    03-19-2013,17:41:18 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,17:41:18 : Loading XML from:
    03-19-2013,17:41:18 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,17:41:18 : RawsDlgSequence::CheckInstMode
    03-19-2013,17:41:18 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,17:41:19 : Launching UI Install
    03-19-2013,17:41:19 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:41:19 : m_bUseNativeClient = 1
    03-19-2013,17:41:19 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:41:20 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,17:41:20 : CopySupportFiles
    03-19-2013,17:41:20 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,17:41:20 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:41:20 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,17:41:20 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,17:41:28 : Typical install value is set to : True
    03-19-2013,17:41:29 : m_bUseNativeClient = 1
    03-19-2013,17:41:29 : Executing SQL_GetServicePack.
    03-19-2013,17:41:29 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:41:29 : Connected to SQL Server.
    03-19-2013,17:41:29 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:41:29 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:41:29 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:41:29 : Connected to SQL Server.
    03-19-2013,17:41:29 : Executing SQL_GetServicePack.
    03-19-2013,17:41:29 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:41:29 : Connected to SQL Server.
    03-19-2013,17:41:29 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:41:29 : m_bUseNativeClient = 1
    03-19-2013,17:41:51 : m_bUseNativeClient = 1
    03-19-2013,17:41:51 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:43:04 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,17:43:04 : Install is not executing as the service account.
    03-19-2013,17:43:04 : Successfully Logged on as service account.
    03-19-2013,17:43:04 : Successfully impersonated service account.
    03-19-2013,17:43:04 : EUserName value successfully written to the registry.
    03-19-2013,17:43:04 : EPassword value successfully written to the registry.
    03-19-2013,17:43:04 : EDomain value successfully written to the registry.
    03-19-2013,17:43:09 : There were no remote computers selected for install
    03-19-2013,17:43:09 : m_bUseNativeClient = 1
    03-19-2013,17:43:09 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,17:43:10 : Terminal Services enabled.
    03-19-2013,17:43:10 : Terminal Services server has been set to Install mode.
    03-19-2013,17:43:11 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,17:43:11 : Executing InstallLiveUpdate.
    03-19-2013,17:44:35 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,17:44:35 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,17:44:35 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,17:44:35 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,17:44:35 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:44:35 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,17:44:35 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:44:35 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,17:44:35 : "C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:44:36 : Starting Install
    03-19-2013,17:44:36 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,17:44:36 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:44:36 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,17:44:36 : Discovered Total Actions: 115
    03-19-2013,17:44:36 : The return code from the MSI is: 1601
    03-19-2013,17:44:36 : Cleaning up the symc status key
    03-19-2013,17:44:36 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,17:44:36 : Clean up Symantec installer keys.
    03-19-2013,17:44:37 : Terminal Services enabled.
    03-19-2013,17:44:37 : Terminal Services server has been set to Execute mode.
    03-19-2013,17:44:57 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,17:44:57 : BeSeqDlgs::DlgInstallComplete
    03-19-2013,17:44:57 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:44:57 : Skipping push of remote servers and agents due to failed local install.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,17:45:25 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:45:28 : Gathering Telemetry items
    03-19-2013,17:45:28 : Failed to start the management service
    03-19-2013,17:45:28 : Service BackupExecManagementService was not found on computer '.'.
    03-19-2013,17:45:28 : Sending Telemetry to Symantec
    03-19-2013,17:45:28 : Transmit Telemetry initialized.
    03-19-2013,17:45:28 : TelemetryRegistryHelpers initialized.
    03-19-2013,17:45:29 : TransmitTelemetry.TransmitMessage URL=http://statsbe.hro.rnd.veritas.com/betelemetry/stats.php, Caught WebException The remote name could not be resolved: 'statsbe.hro.rnd.veritas.com'
    03-19-2013,17:56:31 : Windows Operating System Version: 6.1
    03-19-2013,17:56:31 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,17:56:33 : Executing managed _Setup:
    03-19-2013,17:56:33 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,17:56:33 : Loading XML from:
    03-19-2013,17:56:33 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,17:56:33 : RawsDlgSequence::CheckInstMode
    03-19-2013,17:56:33 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,17:56:34 : Launching UI Install
    03-19-2013,17:56:35 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:56:35 : m_bUseNativeClient = 1
    03-19-2013,17:56:35 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:56:35 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,17:56:35 : CopySupportFiles
    03-19-2013,17:56:35 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,17:56:35 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:56:35 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,17:56:35 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,17:56:49 : Typical install value is set to : True
    03-19-2013,17:56:50 : Executing SQL_GetServicePack.
    03-19-2013,17:56:50 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:56:51 : Connected to SQL Server.
    03-19-2013,17:56:51 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:56:51 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:56:51 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:56:51 : Connected to SQL Server.
    03-19-2013,17:56:51 : Executing SQL_GetServicePack.
    03-19-2013,17:56:51 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:56:51 : Connected to SQL Server.
    03-19-2013,17:56:51 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:57:37 : m_bUseNativeClient = 1
    03-19-2013,17:57:37 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:58:41 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,17:58:41 : Install is not executing as the service account.
    03-19-2013,17:58:41 : Successfully Logged on as service account.
    03-19-2013,17:58:41 : Successfully impersonated service account.
    03-19-2013,17:58:41 : EUserName value successfully written to the registry.
    03-19-2013,17:58:41 : EPassword value successfully written to the registry.
    03-19-2013,17:58:41 : EDomain value successfully written to the registry.
    03-19-2013,17:58:51 : There were no remote computers selected for install
    03-19-2013,17:58:51 : m_bUseNativeClient = 1
    03-19-2013,17:58:51 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,17:58:52 : Terminal Services enabled.
    03-19-2013,17:58:52 : Terminal Services server has been set to Install mode.
    03-19-2013,17:58:52 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,17:58:54 : Executing InstallLiveUpdate.
    03-19-2013,17:59:06 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,17:59:06 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,17:59:07 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,17:59:07 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,17:59:07 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:59:07 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,17:59:07 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:59:07 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,17:59:07 : "C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:59:07 : Starting Install
    03-19-2013,17:59:07 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,17:59:07 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:59:07 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,17:59:08 : Discovered Total Actions: 115
    03-19-2013,17:59:08 : The return code from the MSI is: 1601
    03-19-2013,17:59:08 : Cleaning up the symc status key
    03-19-2013,17:59:08 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,17:59:08 : Clean up Symantec installer keys.
    03-19-2013,17:59:10 : Terminal Services enabled.
    03-19-2013,17:59:10 : Terminal Services server has been set to Execute mode.
    03-19-2013,18:00:01 : The return code is: 0
    03-19-2013,18:00:01 : SUCCESS:  Installation has completed successfully.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:02:24 : Windows Operating System Version: 6.1
    03-19-2013,18:02:24 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:02:26 : Executing managed _Setup:
    03-19-2013,18:02:26 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:02:26 : Loading XML from:
    03-19-2013,18:02:26 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:02:26 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:02:26 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:02:26 : Launching UI Install
    03-19-2013,18:02:26 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:02:26 : m_bUseNativeClient = 1
    03-19-2013,18:02:26 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:02:26 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:02:26 : CopySupportFiles
    03-19-2013,18:02:26 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:02:27 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:02:27 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:02:27 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:03:11 : The return code is: 0
    03-19-2013,18:03:11 : SUCCESS:  Installation has completed successfully.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:03:21 : Windows Operating System Version: 6.1
    03-19-2013,18:03:21 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:03:22 : Windows Operating System Version: 6.1
    03-19-2013,18:03:22 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:03:23 : Executing managed _Setup:
    03-19-2013,18:03:23 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:03:23 : Loading XML from:
    03-19-2013,18:03:23 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:03:23 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:03:23 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:03:24 : Launching UI Install
    03-19-2013,18:03:24 : Executing managed _Setup:
    03-19-2013,18:03:24 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:03:24 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:03:24 : m_bUseNativeClient = 1
    03-19-2013,18:03:24 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:03:24 : Loading XML from:
    03-19-2013,18:03:24 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:03:24 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:03:24 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:03:24 : CopySupportFiles
    03-19-2013,18:03:24 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:03:24 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:03:24 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:03:24 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:03:24 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:03:58 : Typical install value is set to : True
    03-19-2013,18:03:58 : m_bUseNativeClient = 1
    03-19-2013,18:03:58 : Executing SQL_GetServicePack.
    03-19-2013,18:03:58 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:03:58 : Connected to SQL Server.
    03-19-2013,18:03:58 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:03:58 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:03:58 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:03:58 : Connected to SQL Server.
    03-19-2013,18:03:58 : Executing SQL_GetServicePack.
    03-19-2013,18:03:58 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:03:58 : Connected to SQL Server.
    03-19-2013,18:03:58 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:03:58 : m_bUseNativeClient = 1
    03-19-2013,18:04:20 : m_bUseNativeClient = 1
    03-19-2013,18:04:20 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:05:35 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,18:05:35 : Install is not executing as the service account.
    03-19-2013,18:05:35 : Successfully Logged on as service account.
    03-19-2013,18:05:35 : Successfully impersonated service account.
    03-19-2013,18:05:35 : EUserName value successfully written to the registry.
    03-19-2013,18:05:35 : EPassword value successfully written to the registry.
    03-19-2013,18:05:35 : EDomain value successfully written to the registry.
    03-19-2013,18:05:36 : There were no remote computers selected for install
    03-19-2013,18:05:36 : m_bUseNativeClient = 1
    03-19-2013,18:05:36 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,18:05:37 : Terminal Services enabled.
    03-19-2013,18:05:37 : Terminal Services server has been set to Install mode.
    03-19-2013,18:05:37 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,18:05:38 : Executing InstallLiveUpdate.
    03-19-2013,18:05:50 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,18:05:50 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,18:05:50 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,18:05:50 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,18:05:50 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:05:50 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,18:05:50 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:05:50 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,18:05:50 : "C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:05:50 : Starting Install
    03-19-2013,18:05:50 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,18:05:50 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:05:50 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,18:05:50 : Discovered Total Actions: 115
    03-19-2013,18:05:50 : The return code from the MSI is: 1601
    03-19-2013,18:05:51 : Cleaning up the symc status key
    03-19-2013,18:05:51 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,18:05:51 : Clean up Symantec installer keys.
    03-19-2013,18:05:51 : Terminal Services enabled.
    03-19-2013,18:05:51 : Terminal Services server has been set to Execute mode.
    03-19-2013,18:06:32 : The return code is: 0
    03-19-2013,18:06:32 : SUCCESS:  Installation has completed successfully.
    03-19-2013,18:07:36 : Setup is already running.  Unable to initialize another instance of setup.
    03-19-2013,18:07:39 : Error initializing shared data
    03-19-2013,18:07:39 : ERROR:  Installation failed with error 1603. GetLastError = :0
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:13:44 : Windows Operating System Version: 6.1
    03-19-2013,18:13:44 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:13:44 : Windows Operating System Version: 6.1
    03-19-2013,18:13:44 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:13:46 : Executing managed _Setup:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:13:46 : Executing managed _Setup:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:13:46 : Loading XML from:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:13:46 : Loading XML from:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:13:46 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:13:46 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:13:46 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:13:46 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:13:47 : Launching UI Install
    03-19-2013,18:13:47 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:13:48 : m_bUseNativeClient = 1
    03-19-2013,18:13:48 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:13:48 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:13:48 : CopySupportFiles
    03-19-2013,18:13:48 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:13:48 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:13:48 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:13:48 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:13:54 : Typical install value is set to : True
    03-19-2013,18:13:55 : m_bUseNativeClient = 1
    03-19-2013,18:13:55 : Executing SQL_GetServicePack.
    03-19-2013,18:13:55 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:13:56 : Connected to SQL Server.
    03-19-2013,18:13:56 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:13:56 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:13:56 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:13:56 : Connected to SQL Server.
    03-19-2013,18:13:56 : Executing SQL_GetServicePack.
    03-19-2013,18:13:56 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:13:56 : Connected to SQL Server.
    03-19-2013,18:13:56 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:13:56 : m_bUseNativeClient = 1
    03-19-2013,18:14:41 : m_bUseNativeClient = 1
    03-19-2013,18:14:41 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:16:09 : Service account specified is not valid
    03-19-2013,18:16:09 : Unable to authenticate with the user and password information given for ACCENTPRESS\backup.
    03-19-2013,18:16:10 : Error validating service account credentials.
    03-19-2013,18:16:20 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,18:16:20 : Install is not executing as the service account.
    03-19-2013,18:16:20 : Successfully Logged on as service account.
    03-19-2013,18:16:20 : Successfully impersonated service account.
    03-19-2013,18:16:20 : EUserName value successfully written to the registry.
    03-19-2013,18:16:20 : EPassword value successfully written to the registry.
    03-19-2013,18:16:20 : EDomain value successfully written to the registry.
    03-19-2013,18:16:22 : There were no remote computers selected for install
    03-19-2013,18:16:22 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,18:16:23 : Terminal Services enabled.
    03-19-2013,18:16:23 : Terminal Services server has been set to Install mode.
    03-19-2013,18:16:23 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,18:16:25 : Executing InstallLiveUpdate.
    03-19-2013,18:16:37 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,18:16:37 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,18:16:38 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,18:16:38 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,18:16:38 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:16:38 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,18:16:38 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:16:38 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,18:16:38 : "C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:16:38 : Starting Install
    03-19-2013,18:16:38 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,18:16:38 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:16:38 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,18:16:39 : Discovered Total Actions: 115
    03-19-2013,18:16:39 : The return code from the MSI is: 1601
    03-19-2013,18:16:39 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,18:16:39 : Clean up Symantec installer keys.
    03-19-2013,18:16:39 : Cleaning up the symc status key
    03-19-2013,18:16:41 : Terminal Services enabled.
    03-19-2013,18:16:41 : Terminal Services server has been set to Execute mode.
    03-19-2013,18:17:08 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,18:17:08 : BeSeqDlgs::DlgInstallComplete
    03-19-2013,18:17:08 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:17:08 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,18:17:09 : Gathering Telemetry items
    03-19-2013,18:17:09 : Failed to start the management service
    03-19-2013,18:17:09 : Service BackupExecManagementService was not found on computer '.'.
    03-19-2013,18:17:09 : Sending Telemetry to Symantec
    03-19-2013,18:17:09 : Transmit Telemetry initialized.
    03-19-2013,18:17:09 : TelemetryRegistryHelpers initialized.
    03-19-2013,18:17:21 : TransmitTelemetry.TransmitMessage URL=http://statsbe.hro.rnd.veritas.com/betelemetry/stats.php, Caught WebException The remote name could not be resolved: 'statsbe.hro.rnd.veritas.com'
    03-19-2013,18:17:33 : TransmitTelemetry.TransmitMessage URL=http://statsbe.norton.com/n/p, Caught WebException The remote name could not be resolved: 'statsbe.norton.com'
    03-19-2013,18:17:33 : Telemetry transmission failed.  Data was not sent.
    03-19-2013,18:17:33 : The return code is: 1601
    03-19-2013,18:17:33 : ERROR:  Installation failed with error 1601. GetLastError = :0
    03-19-2013,18:17:48 : Setup is already running.  Unable to initialize another instance of setup.
    03-19-2013,18:17:51 : Error initializing shared data
    03-19-2013,18:53:53 : m_bUseNativeClient = 1
    03-19-2013,18:53:53 : Executing SQL_GetServicePack.
    03-19-2013,18:53:53 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:53:54 : Connected to SQL Server.
    03-19-2013,18:53:54 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:53:54 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:53:54 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:53:54 : Connected to SQL Server.
    03-19-2013,18:53:54 : Executing SQL_GetServicePack.
    03-19-2013,18:53:54 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:53:54 : Connected to SQL Server.
    03-19-2013,18:53:54 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:53:54 : m_bUseNativeClient = 1
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:58:06 : Windows Operating System Version: 6.1
    03-19-2013,18:58:06 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:58:08 : Executing managed _Setup:
    03-19-2013,18:58:08 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:58:09 : Loading XML from:
    03-19-2013,18:58:09 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:58:09 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:58:09 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:58:09 : Launching UI Install
    03-19-2013,18:58:10 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:58:10 : m_bUseNativeClient = 1
    03-19-2013,18:58:10 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:58:10 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:58:10 : CopySupportFiles
    03-19-2013,18:58:10 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:58:11 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:58:11 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:58:11 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:58:15 : Typical install value is set to : True
    03-19-2013,18:58:16 : m_bUseNativeClient = 1
    03-19-2013,18:58:16 : Executing SQL_GetServicePack.
    03-19-2013,18:58:16 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:58:16 : Connected to SQL Server.
    03-19-2013,18:58:16 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:58:16 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:58:16 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:58:16 : Connected to SQL Server.
    03-19-2013,18:58:16 : Executing SQL_GetServicePack.
    03-19-2013,18:58:16 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:58:16 : Connected to SQL Server.
    03-19-2013,18:58:16 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:58:16 : m_bUseNativeClient = 1
    03-19-2013,18:58:49 : m_bUseNativeClient = 1
    03-19-2013,18:58:49 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:59:43 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,18:59:43 : Install is not executing as the service account.
    03-19-2013,18:59:43 : Successfully Logged on as service account.
    03-19-2013,18:59:44 : Successfully impersonated service account.
    03-19-2013,18:59:44 : EUserName value successfully written to the registry.
    03-19-2013,18:59:44 : EPassword value successfully written to the registry.
    03-19-2013,18:59:44 : EDomain value successfully written to the registry.
    03-19-2013,18:59:46 : There were no remote computers selected for install
    03-19-2013,18:59:46 : m_bUseNativeClient = 1
    03-19-2013,18:59:46 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,18:59:47 : Terminal Services enabled.
    03-19-2013,18:59:47 : Terminal Services server has been set to Install mode.
    03-19-2013,18:59:47 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,18:59:49 : Executing InstallLiveUpdate.
    03-19-2013,19:00:01 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,19:00:01 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,19:00:01 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,19:00:01 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,19:00:01 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,19:00:01 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,19:00:01 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,19:00:02 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,19:00:02 : "C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,19:00:02 : Starting Install
    03-19-2013,19:00:02 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,19:00:02 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,19:00:02 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,19:00:03 : Discovered Total Actions: 115
    03-19-2013,19:00:03 : The return code from the MSI is: 1601
    03-19-2013,19:00:03 : Cleaning up the symc status key
    03-19-2013,19:00:03 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,19:00:03 : Clean up Symantec installer keys.
    03-19-2013,19:00:05 : Terminal Services enabled.
    03-19-2013,19:00:05 : Terminal Services server has been set to Execute mode.
    03-19-2013,19:00:07 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,19:00:07 : BeSeqDlgs::DlgInstallComplete
    03-19-2013,19:00:07 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,19:00:07 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,19:00:10 : Gathering Telemetry items
    03-19-2013,19:00:10 : Failed to start the management service
    03-19-2013,19:00:10 : Service BackupExecManagementService was not found on computer '.'.
    03-19-2013,19:00:10 : Sending Telemetry to Symantec
    03-19-2013,19:00:10 : Transmit Telemetry initialized.
    03-19-2013,19:00:10 : TelemetryRegistryHelpers initialized.
    03-19-2013,19:00:10 : TransmitTelemetry.TransmitMessage URL=http://statsbe.hro.rnd.veritas.com/betelemetry/stats.php, Caught WebException The remote name could not be resolved: 'statsbe.hro.rnd.veritas.com'
    03-19-2013,19:00:10 : Telemetry data was successfully sent to Symantec
    03-19-2013,19:00:10 : The return code is: 1601
    03-19-2013,19:00:11 : ERROR:  Installation failed with error 1601. GetLastError = :0 
    DJH

  • How Make TS local User Profile After Install Windows 7 without Domain

    Hi,
    I make TS to install Windows 7 Is success But after finish install i cannot login
    If something need to add TS user local profile after install Windows 7 Without Join the Domain And make the user Administrator LocalGroup
    Thank for Help

    Let's start with the fact that you are missing a key element in your task sequence. You need to have the step
    Setup Windows and ConfigMgr to perform the transition from Windows PE to the new operating system. This task sequence step is a required part of any operating system deployment. It installs the Configuration Manager client into the new operating
    system and prepares for the task sequence to continue execution in the new operating system. See also for more information:
    http://technet.microsoft.com/en-us/library/hh846237.aspx#BKMK_SetupWindowsandConfigMgr
    About your screenshots:
    With the first screenshot you not enabling the local administrator. Is that what you want?
    With the second screenshot your only creating a user account and not adding it to the local administrators group. That would need an additional action like this
    cmd.exe /c net localgroup /add administrators User01.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Windows Installer for FlexMotion keeps comming up!

    When I log into my machine as a different user, every time I try and run IE or a VB app, Windows Installer keeps trying to install Flex-Motion again!
    This is a production machine and NOT acceptable!
    How can I get rid of this d*mn thing? I tried installing Flex-Motion again, but now it just gives me "Can connect to network share WinNT\". ARGH!
    How can I fix this without designing out the NI hardware from my system (which I would LOVE to do, for all the crap it's caused me!)

    Nick,
    The reason why the installer will pop-up with IE or VB application is because for some reason your previous installation or operation of the driver broke some file. MAX controls Motion and it is built over IE and VB, so whenever you call this applications it searches registries and founds that there is something wrong with a file in Motion, it will try to go and repair it itself, but since it does not finds the install files it pops up the installer (and the installer searches the registry which as a user you don't have access to), I believe this is the reason also for your message "can't connect to network share...", probably your motion driver was installed from that directory and you don't have access to it as a user. Your best option is to download the files t
    o install the driver to your computer, then log as an administrator, install flexmotion (reinstall), and leave the files there. Log as a user and you should be able to use the motion hardware with no problem. In case you do, then your system may be having other issues that we need to troubleshoot more deeply, we have lots of customers using NT, 2000 and XP with users operating motion without any trouble so we may be facing a more complicated issue.
    If you have any other concerns about NI software or hardware you can also discuss this with us so we can see what is the reason for this issues to happen, and give you the solutions to help you succeed. Developing with unknown hardware or software can be frustrating but at support we look forward to help you out master our products.
    Feel free to contact us, you will find the details at www.ni.com/ask and select "phone NI" from the support options so you can talk with one of us.
    Good luck!
    Regards,
    Nestor Sanchez
    Motion Contro
    l Support
    National Instruments
    Nestor
    National Instruments

  • Adobe reader 10.1 AutoUpdate without administrative privileges

    Hi,
    If I install Adobe Reader 10.1 for windows 7 manually, then standard user without administrative rights can use autoapdate. If I install it through Group Policy or SCCM, then standard users should enter admin's password. How can I install Adobe Reader automatically and that it doesn't demand administrator's password from standard users?

    Well, Let me rephrase, so you want to push the Reader 10.1 via GPO and then afterwards you want the users machines get updated automatically. i.e. Post 10.1, you want the users to receive updates via (Help>Check for updates) silent update and not via GPO. Am I right?
    If this is the case, am not sure if this is an supported scenario, because you are installing an AIP first and then the next updates are coming from an Non AIP installation. As far as I know, if we have deployed any patch via GPO then the next updates must be pushed via GPO only. Since, their underlying technology is AIP. We should not be mixing both the ways of installation.
    I do not think, there's any solution available for your problem via GPO right now. Though I would like to see your Cust Wizard option once. But what I can suggest you to resolve the issue with SCCM (if possible)

  • Installing Office 365 on a different hard drive to that of the windows installation

    Hi Guys,
    I have an office 365 account and was using it succesfully on my pre-installed windows 8. My PC crashed and I re-installed windows 7 on it. I put the windows installation on my 20gb SSD and, as you have guessed, there is very little space left over on it
    for anything else.
    I do understand the technology around the installer etc when you download from office365.com, but is there no way to work/get around this problem and install it to my 500gb HDD?
    Any help would be greatly appreciated as I need my office back up and running for business.

    Alright CharlieWright I think I have a solution to this problem!
    It's weird, and it's kind of hacked together, but it seems to be working. Use this solution at your own risk, I have it working and i'm quite happy with it. With this solution windows basically *thinks* office is where it's supposed to be (C:) but it's not
    there, instead there's an automatic pointer to where it actually is (your other storage device). It's called a junction.. hence the /J later.. anyway, here's what I did:
    1. Create a backup of everything in case this breaks your device. It shouldn't, but you never know.
    2. Download and install LockHunter (lockhunter.com), it's a software I used to simplify the process. Without LockHunter you'll have to manually end process on everything that keeps you from accessing the office directory.
    3. Empty your recycle bin.
    4. Find every directory that office references, I only had one, some people have 2, I don't know if there are ever 3. They're commonly found at:
    C:\Program Files\Microsoft Office 15
    C:\Program Files (x86)\Microsoft Office
    5. Run CMD Prompt as administrator
    6. For each Directory:
    - right click it (ie Microsoft Office 15 folder) and select "what is locking this folder?"
    - unlock it and navigate back to that directory.
    - delete the directory (send it to your recycle bin to relax)
    - in the cmd prompt type: MKLINK /J "Full original directory" "Desired destination directory"
    for example:
    MKLINK /J "C:\Program Files\Microsoft Office 15" "D:\Program Files\Microsoft Office 15"
    MKLINK /J "C:\Program Files (x86)\Microsoft Office" "D:\Program Files (x86)\Microsoft Office"
    7. Create the destination directories manually.
    8. Test the junction, if you did everything right, when you navigate to the original directory it will look like a shortcut folder and clicking it will look as if you're still on the C drive but you're not, you are actually in the destination directory. If
    you did something wrong you'll get an error.
    9. Open your recycle bin, click the directory and click restore

Maybe you are looking for