Задайте вопросЗадайте вопрос
 

ОтвеченоUnattended SCCM Console on Vista machine

  • 23 ноября 2007 г. 13:13Tom Klaver Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    Hello,

     

    I'm trying to install the SCCM Console unattended on a new installed Vista client. I have used the example in the documentation but the installation is failing. I'm using the full product DVD of SCCM.

     

    Used Setup.ini

    [Identification]
    Action=InstallAdminUI

    [Options]
    FullName=SMS Administrator
    OrgName=NWTRADERS

    SMSInstallDir=%ProgramFiles%\SMSAdmin
    ParentSiteServer=SCCMSERVER

    ParentSiteCode=NWT

     

    It looks like, it wants to install a site instead of the Console.

     

    I appreciate it, if anyone could help me in the right direction
    Tom

    Log file: ConfigMgrSetup.log

    ===================== << Starting SMS V4 Server Setup >> =====================
    <11-23-2007 14:07:33> Commandline :
    "\\smsserver\sms_distr$\Microsoft\SCCM 2007\SETUP\SMSSETUP\BIN\I386\SETUP.EXE"  /script console.ini /NOUSERINPUT /HIDDEN
    <11-23-2007 14:07:33> This is 32 bit.
    <11-23-2007 14:07:33> Verifying the Reg for AssetIntelligence Installation
    <11-23-2007 14:07:33> Setting the default CSV folder path
    <11-23-2007 14:07:34> SMS Build Number = 5931
    <11-23-2007 14:07:34> SMS Version = 4.0
    <11-23-2007 14:07:34> SMS Minimum Build Number = 800
    <11-23-2007 14:07:34> Verifying SMS Active Directory Schema Extensions.
    <11-23-2007 14:07:34> DS Root:CN=Schema,CN=Configuration,DC=enterprise,DC=nwtraders,DC=intra
    <11-23-2007 14:07:34> Verifying SMS Active Directory Schema Extensions.
    <11-23-2007 14:07:34> DS Root:CN=Schema,CN=Configuration,DC=enterprise,DC=nwtraders,DC=intra
    <11-23-2007 14:07:34> The /NoUserInput switch is not specified, the /Hidden switch is ignored.
    <11-23-2007 14:07:34> The command line options are /SCRIPT CONSOLE.INI /NOUSERINPUT
    <11-23-2007 14:07:34> Setup has not detected an existing installation of a primary site server, secondary site server, site system, or Configuration Manager console on this computer.

    You cannot install primary or secondary site server components on this computer because it is not a server in a Windows domain.
    <11-23-2007 14:07:34> Error Section Identification key Action in the setup script is either missing or empty.
    <11-23-2007 14:07:34> The ConfigMgr setup script contains syntax errors.

Ответы

Все ответы

  • 24 ноября 2007 г. 0:06WallyMSFT, ВладелецМедали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    Have you tried it manually? You might try that to see if it works.

     

    Also, try to see if it works on an XP system or other operating system.

     

    I've not heard of any issues with this, but never tried an unattended setup of the admin console on Vista, only attended.

  • 24 ноября 2007 г. 11:58Tom Klaver Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    For now the Admin Console is installed manually on a Vista machine. So this works. But I want to advertise the Admin Console in SCCM to all SMS administrators and Helpdesk users. I will try to do a unattended install on a XP machine. I'll let you know if this works.

     

    Thanks Wally for your reply.

    Best regards

    Tom

  • 25 ноября 2007 г. 1:11WallyMSFT, ВладелецМедали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     
    Good to hear that a manual install works for the installation. I have not tried a automated installation of teh admin console, so can't offer much else for help. Try it on XP, and if it doesn't work, we can look at your setup.ini file to see what's missing.

     

  • 4 декабря 2007 г. 11:00Tom Klaver Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    Have tried to install the ConfigMgr Console unattended to a XP machine. Same situation. Made some adjustments to the ini file but still no success. If I look at the log file, the installation thinks it must upgrade the console, but it is a fresh installation.

     

    Used command line: SMSSETUP\BIN\I386\SETUP.EXE" /SCRIPT CONSOLE.INI /PREREQ /UI /HIDDEN

    Used ini file:

     

    [Identification]
    Action=InstallAdminUI

    [Options]
    PrerequisiteComp=1
    PrerequisitePath=\\smsserver\SMS_Distr$\Microsoft\SCCM 2007\Update_download
    FullName=SMS Administrator
    OrgName=Company Name

    SMSInstallDir=%ProgramFiles%\SMSAdmin
    ParentSiteServer=PRDSCCM01
    ParentSiteCode=COD

     

    ConfigMgrSetup.log Log file:

    <12-04-2007 11:44:48>
    ===================== << Starting SMS V4 Server Setup >> =====================
    <12-04-2007 11:44:49> Commandline :
    "\\SMSSERVER\SMS_DP$\SMSPKG\COD00003\SMSSETUP\BIN\I386\SETUP.EXE" /SCRIPT CONSOLE.INI /PREREQ /UI /HIDDEN
    <12-04-2007 11:44:49> This is 32 bit.
    <12-04-2007 11:44:49> Verifying the Reg for AssetIntelligence Installation
    <12-04-2007 11:44:49> Setting the default CSV folder path
    <12-04-2007 11:44:49> SMS Build Number = 5931
    <12-04-2007 11:44:49> SMS Version = 4.0
    <12-04-2007 11:44:49> SMS Minimum Build Number = 800
    <12-04-2007 11:44:49> Verifying SMS Active Directory Schema Extensions.
    <12-04-2007 11:44:49> DS Root:CN=Schema,CN=Configuration,DC=enterprise,DC=loodswezen,DC=intra
    <12-04-2007 11:44:49> Verifying SMS Active Directory Schema Extensions.
    <12-04-2007 11:44:49> DS Root:CN=Schema,CN=Configuration,DC=enterprise,DC=loodswezen,DC=intra
    <12-04-2007 11:44:49> The /NoUserInput switch is not specified, the /Hidden switch is ignored.
    <12-04-2007 11:44:49> The command line options are /PREREQ /UI /SCRIPT CONSOLE.INI
    <12-04-2007 11:44:49> Setup has not detected an existing installation of a primary site server, secondary site server, site system, or Configuration Manager console on this computer.

    You cannot install primary or secondary site server components on this computer because it is not a server in a Windows domain.
    <12-04-2007 11:44:53> The ConfigMgr setup script contains syntax errors.

  • 4 декабря 2007 г. 17:32WallyMSFT, ВладелецМедали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    The /prereq is used to validate the prerequisites prior to an installation, not with a scripted install. Try taking the "/prereq /UI" out and then run the script.

     

    Or to just validate prereqs, take out the script and hidden params.

  • 5 декабря 2007 г. 12:23Jevgenijs Geizans Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     Отвечено

    Hi Tom

     

    You need more one string in Options section

    SDKServer=servername

     

    My adminui.ini

    [Identification]

    Action=InstallAdminUI

    [Options]
    SiteCode=*
    SMSInstallDir=C:\SCCMConsole
    ParentSiteServer=*
    SDKServer=*

     

    install string

    "*\BIN\I386\setup.exe" /script "*\Adminui.ini"

    Don't forget wimgapi

     

    and if You will get problem with status messages

     

    install VCREDIST_X86.EXE from SCCM disk

    (I don't know why, but VCREDIST_X86.EXE from microsoft download don't resolve problem)

     

    best regards

    Jevgenijs Geizans

  • 28 марта 2008 г. 16:16scarneol Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    In my case, unattended installs of the SCCM Admin Console only work with Windows XP systems. For some reason, Vista and Vista SP1 systems hang. MUST INSTALL MANUALLY FOR NOW.

     

    Looking at the log <ConfigMgrSetup.log>

    Hangs at:

    “The command line options are /SCRIPT \\SMSSERVER\SMSSETUP\Adminui.ini /nouserinput”

     

    Make sure you use the Full Path to the script file and use "quotes" if the path contains any spaces...da 

  • 15 мая 2008 г. 11:41DougThomson Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

     

    unattended install to vista works OK

     

    create a package using a copy of the sccm disk as the source and SMSSETUP folder as the root

     

    create an ini file 'console_unattended.ini' with contents

     

    [Identification]
    Action=InstallAdminUI
    [Options]
    SMSInstallDir=c:\SMSADMIN
    ParentSiteServer=your_primarty_site_code
    SDKServer=your_primary_server_name

     

     

    create a cmd file 'console_unattended.cmd' contents

     

    %~dp0\bin\i386\setup.exe /script %~dp0\console_unattended.ini

     

    copy above two files to SMSSETUP folder in the source

     

    package program line is 'console_unattended.cmd'

     

    advertise with run from dp

     

     

  • 1 июля 2008 г. 1:22Danny Andrijanic Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    Thanks Doug.

     

    That's working for me.

  • 1 июля 2009 г. 9:04JohnNMason Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     

    the console installs ok but when I run it as my user I get a program error saying MMc encountered a problem and needed to close

    when I run as Admin it just hangs connecting

    [Identification]
    Action=InstallAdminUI
    [Options]
    SMSInstallDir=c:\SMSADMIN
    ParentSiteServer=ABH
    SDKServer=Networkmgmt

    that is my ini file

    any ideas what could be wrong

    thanks

  • 1 июля 2009 г. 11:14JohnNMason Медали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     
    This is the error i get from the log in any one can help

    \r\nSystem.Runtime.InteropServices.COMException\r\nThe RPC server is unavailable. (Exception from HRESULT: 0x800706BA)\r\n   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
  • 6 июля 2009 г. 17:55WallyMSFT, ВладелецМедали пользователяМедали пользователяМедали пользователяМедали пользователяМедали пользователя
     
    Have you tried a manual install of the console to see if the issue is with your deployment?

    By the way, it is usually best to start a new thread when you have an issue instead of adding onto a very old thread that has been marked as answered. I know some people stop looking at threads that have been marked as answered :-)
    Wally Mead