ThinInstal​ler problems with SCCM

Hi,
I am having very frustrating problems with ThinInstaller.  I am trying to deploy drivers to a Thinkpad with ThinInstaller via SCCM.  Hope anyone with experience of it working or any experience of ThinInstaller in general can help.
I am not too sure where the problem lies, although I think it is mainly with ThinInstaller.  I am quite new to both SCCM and to ThinInstaller so I have built up what I have for it using what I found on the Internet.
SCCM Setup
I have a Task Sequence setup to initially install the Networking and Storage drivers, this works ok.  The machine adds to the domain without any problem.  Then I run the commands in the screenshot below.
Task Sequence
Step 1 – Run ThinInstaller Trustzone
%Windir%\Microsoft.NET\Framework\v2.0.50727\CasPol​.exe -pp off -m -ag 1.2 -url file://\\192.168.100.236\PackageSource\OSDDrivers\​Win7x86\LenovoT420-4236JDO FullTrust
Step 2 – CMD CP ThinInstaller
I run the following command line;
cmd.exe /c xcopy.exe "\\192.168.100.236\smspkge$\SHR0012E\*.*" C:\Lenovo\thininstaller\ /E /D
It gets passed this step; I can see the C:\Lenovo\ThinInstaller folder
Step 3 – CMD Run Thininstaller
I run the following command line;
cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\192.168.100.236\PackageSource\OSDDrivers\Win7x86​\LenovoT420-4236JDO -noicon -includerebootpackages 1,2,3,4
This step doesn’t seem to work. 
I have pasted in sections of the Task Sequence as well as details of my ThinInstaller setup below;
Part of ThinInstaller error log
[Thin Installer build: 2009-12-09 Version: 1.1.0005]            5/31/2012 12:09:09 PM
Info        2012-05-31 , 12:09:09
                at Tvsu.Environment.EnvironmentManager..ctor()
                Message: Starting Environment Manager...
Info        2012-05-31 , 12:09:09
                at Tvsu.Nls.NlsResources..ctor()
                Message: Starting the instance of NLS@Runtime
Info        2012-05-31 , 12:09:09
                at Tvsu.Nls.NlsResources..ctor()
                Message:
The active language is: EN
The default language is: EN
The OS language is: EN
The language loaded type is: Override
Info        2012-05-31 , 12:09:09
                at Tvsu.CommandLine.CommandLineParameters.ValidateArg​uments(String[] args)
                Message: Validating arguments: System.String[]
Info        2012-05-31 , 12:09:09
                at Tvsu.CommandLine.CommandLineParameters.ValidateArg​uments(String[] args)
                Message: The command is: /CM -searchA-actionINSTALL
Info        2012-05-31 , 12:09:09
                at Tvsu.CommandLine.CommandLineParameters.SearchForUp​dates()
                Message: Searching for Updates: A
Info        2012-05-31 , 12:09:09
                at Tvsu.CommandLine.CommandLineParameters.SearchForUp​dates()
                Message: Notify method: INSTALL
Severe  2012-05-31 , 12:09:09
                at Tvsu.Sdk.SuSdk.StartApplication()
                Message: Application runs with the framework: 2.0.50727.4927
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.DataBase.InitializeDataBase()
                Message: Initializing the DataBase from file: updates.ser
Info        2012-05-31 , 12:09:09
                at Tvsu.Sdk.SuSdk.StartApplication()
                Message: Starting the Application
Info        2012-05-31 , 12:09:09
                at Tvsu.Sdk.SuSdk.GetSystemProperties()
                Message: Get the System Properties
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.StartExecution()
                Message: PreTask
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.StartExecution()
                Message: Start
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Starting the task
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: The current process is:HelloProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the PreProcess HelloProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the StartProcess HelloProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Process.HelloProcess.Start()
                Message: HelloProcess Started
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Process.HelloProcess.Start()
                Message: MTM is: 4236JD0
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Process.HelloProcess.Start()
                Message: Data to be set in the Environment Manager to use with Quest:
QOS (Quest OS): Windows 7
QOSLang (Quest language): EN
MTM: 4236JD0
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the PostProcess HelloProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: The process HelloProcesshas been finished.
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.StartExecution()
                Message: PostTask
Info        2012-05-31 , 12:09:09
                at Tvsu.Sdk.SuSdk.GetSystemProperties()
                Message: Return the System Properties
Info        2012-05-31 , 12:09:09
                at Tvsu.CommandLine.CommandLineParameters.SearchForUp​dates()
                Message: The System Properties are:
4236JD0
Windows 7
EN
Info        2012-05-31 , 12:09:09
                at Tvsu.Sdk.SuSdk.GetApplicableUpdates(searchingFolde​rDelegate spd, showErrMsgDelegate sed)
                Message: Get Applicable Updates
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.StartExecution()
                Message: PreTask
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.StartExecution()
                Message: Start
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Starting the task
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: The current process is:HelpCenterIndexRepositoryProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the PreProcess HelpCenterIndexRepositoryProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Process.HelpCenterIndexRepositoryProce​ss.PreProcess()
                Message: 'Share name' to use: \\192.168.100.236\PackageSource\OSDDrivers\Win7x86​\LenovoT420-4236JDO\
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the StartProcess HelpCenterIndexRepositoryProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Process.HelpCenterIndexRepositoryProce​ss.LaunchEgather()
                Message: Launching Egather
Info        2012-05-31 , 12:09:09
                at Tvsu.Egather.EgatherManager.GetEgatherParser(Strin​g type)
                Message: Running egather complete.....
Info        2012-05-31 , 12:09:09
                at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabas​eManager.GetDescriptors(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
                Message: Received data -> ShareName: \\192.168.100.236\PackageSource\OSDDrivers\Win7x86​\LenovoT420-4236JDO\, Agent:
Info        2012-05-31 , 12:09:09
                at Tvsu.Egather.EgatherExecutor.RunAsWindowsService(S​tring directory, String command, String arguments)
                Message: I received this info:
Directory: C:\Lenovo\ThinInstaller\egather\
Command: ia.exe
Arguments: -filename"C:\Lenovo\ThinInstaller\egather\sysreco" -silent -local -section SYSTEM_SUMMARY REGIONAL_SETTINGS SMBIOS_INFORMATION Firmware_Information Installed_Software SMBIOS_INFORMATION DEVICE_DRIVERS_AND_SERVICES IDE_DEVICE_INFORMATION DEVICE_MANAGER_SETTINGS -p device_manager enable_hardwareid
Info        2012-05-31 , 12:09:09
                at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(S​tring dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
                Message: Directory: C:\Lenovo\ThinInstaller\egather\
Command: ia.exe
Arguments: -filename"C:\Lenovo\ThinInstaller\egather\sysreco" -silent -local -section SYSTEM_SUMMARY REGIONAL_SETTINGS SMBIOS_INFORMATION Firmware_Information Installed_Software SMBIOS_INFORMATION DEVICE_DRIVERS_AND_SERVICES IDE_DEVICE_INFORMATION DEVICE_MANAGER_SETTINGS -p device_manager enable_hardwareid
Install type: COMMAND
TimeOut: 300000
HideWindow?: True
Info        2012-05-31 , 12:09:09
                at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(S​tring dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
                Message: Directory 1: C:\Lenovo\ThinInstaller\egather\
Info        2012-05-31 , 12:09:09
                at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(S​tring dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
                Message: If directory 1 exists: C:\Lenovo\ThinInstaller\egather\
Info        2012-05-31 , 12:09:09
                at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(S​tring dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
                Message: The parameters directory and command stay as follows:
Command: ia.exe
Directory: C:\Lenovo\ThinInstaller\egather\
Info        2012-05-31 , 12:09:09
                at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(S​tring dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
                Message: Type hidden
Info        2012-05-31 , 12:09:09
                at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabas​eManager.GetDescrips(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
                Message: The database.xml file was found in \\192.168.100.236\PackageSource\OSDDrivers\Win7x86​\LenovoT420-4236JDO\
Info        2012-05-31 , 12:09:09
                at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabas​eManager.GetDescrips(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
                Message: Processing the data base xml file
Info        2012-05-31 , 12:09:09
                at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabas​eManager.GetDescrips(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
                Message: Processing the data base schema file
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the PostProcess HelpCenterIndexRepositoryProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: The size for the UpdateResponse is 32
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: The process HelpCenterIndexRepositoryProcesshas been finished.
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: The current process isescriptorLoaderProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the PreProcess DescriptorLoaderProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Task.Task.Start()
                Message: Executing the StartProcess DescriptorLoaderProcess
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Process.DescriptorLoaderProcess.Start(​)
                Message: Failed to get the file Object reference not set to an instance of an object.
Info        2012-05-31 , 12:09:09
                at Tvsu.Engine.Process.DescriptorLoaderProcess.Start(​)
                Message: Failed to get the file Object reference not set to an instance of an object.
Info        2012-05-31 , 12:09:10
                at Tvsu.Sdk.SuSdk.ShutDownApplication()
                Message: Shut Down the Application
ThinInstaller.exe.configuration
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
                <RepositoryPath></RepositoryPath>
                <LogPath>C:\Lenovo\ThinInstaller\ExtraLogs</LogPat​h>
                <LanguageOverride>EN</LanguageOverride>
                <BlockSize>4096</BlockSize>
                <AskBeforeClosing>NO</AskBeforeClosing>
                <DisplayLicenseNotice>NO</DisplayLicenseNotice>
                <IgnoreLocalLicense>YES</IgnoreLocalLicense>
                <IgnoreRMLicCRCSize>YES</IgnoreRMLicCRCSize>
                <DebugEnable>NO</DebugEnable>
                <ContentMode>Active</ContentMode>
</configuration>
Task Sequence Error
Failed to run the action: CMD Run ThinInstaller.
Incorrect function. (Error: 00000001; Source: Windows)

Create a Folder Applications in Microsoft Deployment Kit
Copy de application ThinInstaller in this folder
Install Lenovo "Update Retriever" on a Windows Machine.
Configure  Lenovo "Update Retriever"  for download the Drivers  
Modify  the Repository  with;
Close "Update Retriever" and go to the location of your Repository folder on the machine
Copy this folder to the \ThinInstaller folder that you create in  Microsoft Deployment Kit
Example: ...\Microsoft Deployment Toolkit  2012\Applications\ThinInstaller
Update sccm dp's
Sccm Task Sequence
Create a Task Sequence lines after Setup Windows and ConfigMgr
Example:
Run Command Line
Apply - Lenovo Driver Based Applications (01) and Apply - Lenovo Driver Based Applications (02)
You need run this twice because there are dependency on the drives package’s
More info let me know
Maarten

Similar Messages

  • Problem with SCCM 2012 R2 Component status messages

    Hello,
    I have a strange problem with Component status messages. When I try to view all messages from any component, I receive an error message stating that the data could not be recieved from the database. Reporting point is installed.
    And when I try to run a report, nothing happens. The report doesn't run.
    Any idea??

    Oooopsss... Status messages disappeared again !! nothing suspect in srsrp.log and compmon.log.
    There are these entries in compsumm.log that got my attention
    The machine account will be used for ["Display=\\DataBaseServer.domain\"]MSWNET:["SMS_SITE=CPS"]\\DataBaseServer.domain\.~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.643+300><thread=3152 (0xC50)>
    Successfully made a network connection to \\DataBaseServer.domain\ADMIN$.~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.643+300><thread=3152 (0xC50)>
    Failed to read Operations Management component registry key values on DataBaseServer.domain; error = 5 (0x5).~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.909+300><thread=3152 (0xC50)>
    Failed to read in current property values and initialize COpsMgmtComponent object; error = 5 (0x5).~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.909+300><thread=3152 (0xC50)>
    Error: Failed to initialize the COpsMgmtComponent object for component SMS_SITE_SQL_BACKUP_S206UT24.CSDPS.QC.CA on machine DataBaseServer.domain. : L’opération a réussi.~~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.909+300><thread=3152
    (0xC50)>

  • OoB Problems with SCCM 2012 SP1 CU1

    Hi around, perhaps somone has tried this things out already and has a little hint for me.
    After we got OoB Managment to work under SCCM 2007 we switched to SCCM 2012 now i have some problems bringing it to work again.
    We use a Verisign Certificate for Provisioning, the Firewall Ports (9971 on Server and 19992, 16993 and 16995 on Client) are opend. The autoenrollment is active. DHCP 06 and 15 are set and configured.
    The IIS SSL Settings are configured to accept Client Certificates and the Bindings are set to the Web Server Template. We tried to configure it using the Verisign Certificate but it didn't work that way either.
    The Webserver Template is build after the Step by Step guide from MS.
    The Verisign Certificate was build the same way, Organization Unit is set to Intel(R) Client Setup Certificate. It was imported in the Personal Certificate Store, exported and implemented in the Enrollment Point.
    The AD Group exists and the Oob Managment Server has the permissions it needs.
    The Oob Managment Point was configured like shown in the MS Step by Step guide.
    The Client i'm testing with was fully unprovisioned.
    Now the only Status i get is detected and when i try to discover AMT the amtopmgr.log brings the following errors.
    Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    **** Error 0x1e5ab3d0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    **** Error 0x1e5ab3d0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    session params : https://OurMachine.test.de:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    session params : https://OurMachine.test.de:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    session params : https://OurMachine.test.de:16993 , 484001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    DoKerberosWSManDiscovery failed. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    session params : https://10.37.135.52:16993 , 15001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    session params : https://10.37.135.52:16993 , 15001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    Discovery to IP address 10.37.135.52 succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    CSMSAMTDiscoveryTask::Execute, discovery to OurMachine succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    CSMSAMTDiscoveryTask::Execute - DDR written to D:\CM2012\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='OurMachine.test.de' P2='' P3='' P4='' P5='' SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    CStateMsgReporter::DeliverMessages - Created state message file: D:\CM2012\inboxes\auth\statesys.box\incoming\vww2tcjc.SMX SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    General Worker Thread Pool: Succeed to run the task OurMachine.test.de. Remove it from task list. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    General Worker Thread Pool: Work thread 3624 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    General Worker Thread Pool: Work thread 3624 exiting. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
    General Worker Thread Pool: Current size of the thread pool is 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 9236 (0x2414)
    We double checked the admin Account in the OOB settings but the password is right and i can manually log in to the MEBX with it.
    Has anyone some suggestions what could be wrong?
    Thank's for the help.

    Yes, I know this is an old post, but I’m trying to clean them up.
    Did you solve this problem, if so what was the solution?
    By the sounds of thing the problem is with your certificate. Can you manually provision a Certified to any of these systems?
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • "Could not connect to the ConfigMgr site database" problem with SCCM

    The scenario is:
    - SCCM 2007 SP1 installed on one server
    - SQL 2008 installed on the other server
    - Console was also installed on the SCCM server.
    Everything was working just fine for about three months. As of few days ago, out of nowhere, I cannot open the console at all, it gives me this error:
    " The ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both
    the ConfigMgr site server and SMS Provider computers. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console Connections" in ConfigMgr Help. "
    I confirmed all permissions (DCOM) and group settings (SMS Admin) and everything looks fine. I also noticed one other thing and I have a feeling its related - I log on to SCCM server and then from there I try to start RDP
    connection to SQL server. I can connect, but as soon as I move the mouse or try clicking somewhere it breaks the connection and the "Trying to re-connect" window appears. It can`t establish normal RDP connection. If I try from any other server to SQL, it works
    fine...
    Any suggestions will be appreciated.
    Dino

    looks like I celebrated way too early - after working for about 20 minutes, it started throwing the same error again. Th adminUI log has this entry:
    ===========================================================================================================0
    [3][13.4.2011 13:33:45] :Error returned from WMI Query Engine\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe ConfigMgr Provider reported an error connecting to the ConfigMgr site database server. Verify
    that the SQL Server is online and that ConfigMgr site server computer account is an administrator on the ConfigMgr site database server.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryProcessor.ProcessQueryWorker(AsyncOperationDatabase asyncData)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)\r\nConfigMgr Error Object:
    instance of SMS_ExtendedStatus
        CauseInfo = "";
        Description = "Unable to get SQL connection.";
        ErrorCode = 3242263810;
        File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspobjectquery.cpp";
        Line = 1861;
        Operation = "ExecQuery";
        ParameterInfo = "select * from SMS_ConfigurationBaselineInfo where UPPER(CI_UniqueID) NOT IN (SELECT UPPER(InstanceKey) FROM SMS_ObjectContainerItem WHERE ObjectType=2011) ORDER BY LocalizedDisplayName";
        ProviderName = "WinMgmt";
        SQLMessage = "[08S01][11][Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.";
        SQLSeverity = 0;
        SQLStatus = 11;
        StatusCode = 2147749889;
    Unable to get SQL connection.
    \r\nSystem.Management.ManagementException\r\nGeneric failure \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()\r\nManagementException details:
    instance of SMS_ExtendedStatus
        CauseInfo = "";
        Description = "Unable to get SQL connection.";
        ErrorCode = 3242263810;
        File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspobjectquery.cpp";
        Line = 1861;
        Operation = "ExecQuery";
        ParameterInfo = "select * from SMS_ConfigurationBaselineInfo where UPPER(CI_UniqueID) NOT IN (SELECT UPPER(InstanceKey) FROM SMS_ObjectContainerItem WHERE ObjectType=2011) ORDER BY LocalizedDisplayName";
        ProviderName = "WinMgmt";
        SQLMessage = "[08S01][11][Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.";
        SQLSeverity = 0;
        SQLStatus = 11;
        StatusCode = 2147749889;
    \r\n
    ====================================================================================================
    As I mentioned in my first post, the RDP from SCCM to SQL servers is not working and I think that is related to my problem....suggestions?

  • Problems with SCCM client instalaltion after upgrade to R2 version

    Hi,
    Few days ago, I have upgraded SCCM 2012 Sp1+CU3 to SCCM 2012 R2. I see now manyy issies in component manager with SMS_EXECUTIVE and SMS_MP_CONTROL_MANAGER. Reaon of this is automatically process of installation SCCM client in latest version. This same
    issue apppear when I trying install SCCM manually. In both cases I have got in ccmsetup.log this:
    CcmCreateEmbeddedClientState. Creates the client state file, which is needed for write filter handing.
    CcmCreateEmbeddedClientStateRollback. Rolls back the action of creating the client state file.
    RegisterExtensionInfo. Registering extension servers
    WriteRegistryValues. Writing system registry values
    Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls.   Verify that you have sufficient access to that key, or contact your support personnel.
    Rollback. Rolling back action:
    Computer where I want install SCCM client, my adm account, Primary site server or NT SERVICE\TrustedInstaller has full right to this registry key but log file record is always this same. 
    AV and Firewall turned off. 
    What next?

    Hi Torsten,
    I have checked client.msi.log and there is this same:
    Note: 1: 1401 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls 3: 5 
    Product: Configuration Manager Client -- Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls.  System error .  Verify that you have sufficient access to that key, or
    contact your support personnel.
    Error 1406. Could not write value SMSCFGRC to key \SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cpls.  System error .  Verify that you have sufficient access to that key, or contact your support personnel.
    User policy value 'DisableRollback' is 0
    Machine policy value 'DisableRollback' is 0
    InstallFinalize. Return value 3.

  • Problem with SCCM console and Windows 8.1

    Can't start SCCM 2012 console in Windows 8.1.
    It can't connect to SCCM site.
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr10\AdminUI\QueryProcessors\WQL]
    "Assembly Path"="C:\\Program Files (x86)\\Microsoft Configuration Manager\\AdminConsole\\bin\\AdminUI.WqlQueryEngine.dll"
    "Depends On"=""
    "Type"="Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager"
    This doesn't help.

    Windows 8.1 is not supported for the ConfigMgr 2012 SP1 Console.
    See for a complete list:
    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigConsoleReq
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Problem with SCCM 2012

    Is there any way to enter the system center configuration manager 2012, some manual data equipment such as: I want to enter data for any IP phone that is not detected on the network or a printer not detected on the network, this possible to manually enter
    data on any device SCCM.

    Hi,
    It sounds like a task for System Center 2012 Service Manager instead which actually has a CMDB in the product.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Problems with report builder 3.0 in SCCM 2012 R2 CU2

    Hi All
    I have problems with editing  (Using Report builder) existing reports  or creating new ones in SCCM 2012 R2 CU2
    We version of SQL we use is SQL 2008 R2 SP2
    I already asked this question in the SCCM 2012 forum but the problem is not related to SCCM but has something to do with application report builder
    I changed the registry key and edited the Microsoft.ConfigurationManagement.exe.config.xml as described in the following link
    http://blogs.technet.com/b/smartinez/archive/2012/07/03/system-center-2012-configuration-manager-create-report-don-t-work-what-do-i-do-now.aspx
    Afterwards I try to edit an report I see report builder is being downloaded and after it generates the following error “Application did not succeed. Unable to continue”
    Error details are
    Following errors were detected during this operation.
    * [22-7-2014 13:55:07] System.Deployment.Application.InvalidDeploymentException (HashValidation)
    - File, Microsoft.DataWarehouse.dll, has a different computed hash than specified in manifest.
    - Source: System.Deployment
    - Stack trace:
    at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
    at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
    at System.Deployment.Application.ComponentVerifier.VerifyComponents()
    at
    System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions
    options)
    at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
    at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
    at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
    at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
    And in the SmsAdminUI.log I noticed the following error
    [16, PID:4460][07/21/2014 14:11:43] :[ReportProxy] - User-specified default Reporting Point [Server1.local.nl] could not be found, [Server2.local.nl] is now the default Reporting Point.
    [1, PID:4460][07/21/2014 14:11:11] :System.InvalidOperationException\r\nThere is an error in XML document (1, 1).\r\n at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
    I removed the reporting point no luck -> I already installed report builder 3.0 local on my computer still no luck.
    I hope someone can give me some advice , I am lost with this error
    Thx in advance
    Regards
    Johan

    Hi Miss Katherine,
    1. I went through the SQL steps in the link you posted
    2. I updated the Reg Key and Microsoft.ConfigurationManagement.exe.config file with 3.0 on both the
    server and the console machine.
    3. I copied the .DLL file from your OneDrive and replaced the existing one on the server.
    4. I uninstalled and re-installed the reporting role on the server and received the 1015 in the log.
    5. I restarted the server and the client machine
    I do get a slightly different error now after using the new DLL
    Errors With Original DLL
    ERROR DETAILS
    * [9/30/2014 8:42:03 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
    - File, Microsoft.DataWarehouse.dll, has a different computed hash than specified in manifest.
    - Source: System.DeploymentERROR DETAILS
    Errors With New DLL
    ERROR DETAILS
    Following errors were detected during this operation.
    * [9/30/2014 9:17:13 AM] System.Deployment.Application.InvalidDeploymentException (RefDefValidation)
    - Reference in the manifest does not match the identity of the downloaded assembly Microsoft.DataWarehouse.dll.
    - Source: System.Deployment

  • SCCM 2012 Update Group inconsistency Problem with Red marked Updates

    Hi everybody,
    we have a big Problem with our SCCM 2012 R2 CU3 Enviroment, regarding of Update Groups which got out of sync.
    we have a SCCM Site Infastructure with one CAS and 4 Primary Sites and on every Site is the SUP Role installed.
    I don't know when this failure occours but i think it was after the CU3 Installation. The Installation itself went smooth without any Errors or Warnings.
    The Problem is as following. We have some updates in Update Groups (all of them are Core XML Updates) which are out of sync and marked red as an invalid Update on 2 Primary Sites. On the CAS Site and the 2 other Primary SItes they are marked as green (downloaded
    yes and deployed yes)
    We have no Replication issues regarding the Replication Status (everything is synchronized to 100%) and the Replication Link Analyzer does also show no Problems at all.
    I now deleted the Deployments and the SW Update Group waited until the replication was fine and created a new one and downloaded these patches on one of the Primary Sites which had shown this Failure.
    The Result was not good. It looks like before. On the CAS and 2 Primary Sites the Deplyment is shown as downloaded but on the other 2 Sites the Status is again Downloaded=no.
    Does anybody have any idea what to do now ? I checked objmgr.log and rcmctr. log but found nothing what shows me the way in the right direction.
    Thx for your time, and it would be fine if anybody can share knowledge about this failure and how to fix it.
    All other Ideas are also welcome.
    Thx a lot in advance and have a nice bug free day :-)
    Bastian

    Hi,
    Please try to manually synchronize software updates from the CAS and monitor the WSUSCtrl.log, WCM.log and wsyncmgr.log on the CAS and Primary sites.
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Problem with update SCCM client to Sp1 CU3 on Windows 2008 server

    Hi all,
    I have problem with update SCCM client on Windows 2008 Server to 2012 Sp1 CU3. I have sent to deployment package with update (SP1 Cumulative Update 3 - server update) on four servers and after few minutes I have got in Monitoring\Deployment details four
    this same errors in "Asset Details":
    USER Message ID
    Status type Description
    NT\AUTHORITY\SYSTEM  1006
    Error 3003
    I love that types of error... which is har to find answer on google :-( I have tried but I haven't find any constructive :-( Did you met with something similar? Which log I should check (sorry - I'm still noob in SCCM2012) to update actual SCCM Client SP1
    (5.00.7804.1000) to SP1 CU3 (5.00.7804.1400)? 
    Thank you.

    I see in fodler with CU3 updates, are four packages:
    - SP1 Cumulative update 3 - x64 client update
    - SP1 Cumulative update 3 - x86 client update
    - SP1 Cumulative update 3 - server update 
    - SP1 Cumulative update 3 - console update
    It will be stupid but... maybe I should deploy x64 client update package? 

  • Problems with E531 network drivers in SCCM 2012 R2

    We are having some serious issues with SCCM 2012 R2 operating system deployment (Windows 7) and the Thinkpad Edge E531 laptop - network drivers are not being applied during the imaging process. Do SCCM driver packages exist for this laptop?
    I downloaded the ethernet drivers manually from here, extracted the files from the executable, imported the drivers into SCCM (it found them), and created a driver package for this model. I also added the drivers to the boot images.
    I do not have an issue during the PXE phase, it is only during the Windows phase - and the laptop is unable to join the domain because it does not have network drivers. 
    In the OSD Task Sequence, I have tried both the auto-apply device drivers rule (default), and creating a special rule for Lenovo E531 with the WMI query: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%6885YU%" . The task sequences all work perfectly on virtual machines, so I am fairly certain this is a driver issue. I have tried Windows 7 x86, x64, and Windows 8.1 x64.
    Any thoughts are welcome - I am new to this particular school district and have never deployed Lenovo in my previous environments. I am about to select a model for this year's laptop purchases and at this point, I am backing away from Lenovo due to this issue.

    We do not create SCCM driver packs for the Edge line of products.  As an alternative you can use Update Retriever to download hardware drivers for a selected model and then use the Export feature to create a folder containing the source files for the drivers.  This can then be used in the Driver Import Wizard which will locate the INF files and only import the files referenced by the INF files.
    You mention you are using SCCM 2012 R2.  This means you should be using the Windows ADK for 8.1 which also means your boot images should be using Windows PE 5.  For your boot images you should be using the Windows 8.1 driver (http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/herr01ww.exe)
    In your OSD task sequence you need to be deploying Windows 7 drivers (http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/her101ww.exe)
    Make sure you keep these separate.  Meaning you should have a driver package for the Windows 7 drivers that you reference in an Apply Drivers task and this package should not include the Windows 8.1 drivers.  Add just the 8.1 drivers to the boot image.

  • Deploying CC Enterprise Applications With SCCM 2012

    Hi all,
    We are using CC Packager to package up individual applications (Photoshop, InDesign etc) and are having trouble deploying the applications once packaged. To deploy, we are using SCCM 2012 and are deploying to Windows 7 x64 clients. It appears that the install begins on the client, then hangs, never to finish.
    We are running the MSI with the REBOOT=ReallySuppress and MSIRESTARTMANAGERCONTROL=Disable commands, but with no luck.
    This has us really stumped. The applications seem to package fine, yet just won't install. If we manually run the installer, we can see it begin installing, then the progress bar goes backwards and the installation ends without displaying any sort of message.
    Also, as an FYI, we have followed this guide closely in our attempts: http://helpx.adobe.com/creative-cloud/packager/deploying-packages-sccm.html
    Has anyone experienced a similar problem? Any ideas?
    Thank you in advance.
    Ryan

    Windows 7 x64 Clients
    Deploying with SCCM 2012
    I have called Adobe before and was told that the application package needs to be on a local drive on the computer. The package cannot be installed if the package is sitting on the network. My installation for a adobe creative cloud  package fails to install when I try to install the application from the software center. At some moment the installation searches to ensure it is on a local disk. Not sure how this happends. If you place the installation package on a drive on your computer the package will install, although it will take time depending on how many applications you have packaged.
    Another problem that you might have is having users log out of the applications without admin previlages.
    I have yet to find a solution for these two problems, I could really use some help from someone who has sucessfully deployed a creative cloud package to a user.
    Thank you

  • For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

    While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
    Background:
    I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
    After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
    1.  Uninstall the OCS 2007 R2 client
    2.  Install all prerequisites for the Lync client
    3.  Install Lync on all user workstations silently.
    While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx".  Well, my response is, I
    tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
    start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them.  I was unable to find any switch or option to prevent the automatic launch.  I suppose the simple solution to that would
    be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
    The next simplest answer I saw was, "extract the MSI and use that with the right switches".  Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
    the MSI to be used or a hacked MSI that bypasses the registry key check.  I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly.  The other problem I ran into
    was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations.  It was this problem that ultimately led me to the solution that I'm about to detail and that has
    worked marvellously for us.
    Solution:
    As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install.  My first attempt was
    just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped.  So, my next attempt was to extract all the prerequisite
    files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
    In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique.  That's where you have, for example, 3 or more programs that run in a package
    in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order.  So, I created programs to 1) kill Communicator.exe 2) uninstall
    Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client.  That final step was always the point of failure because
    I couldn't get the hacked MSI for the Lync Client install to work.  I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error.  That's one of the downsides
    of program-chaining, if one step fails, SCCM completely bails on the deployment.  This is what also led me to the key to my solution:  TASK SEQUENCES.
    I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments. 
    One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running.  Another advantage is that task sequences have some very good built-in conditionals that
    you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine.  Both of those advantages factor highly into my solution.
    OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
    First, you need to extract all the files from the LyncSetup.exe for your needed architectures.  We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account.  To extract the files, just start up
    the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location.  The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
    both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
    or rename them to reflect the architecture).
    For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
    Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server.  Go to the SCCM console into Computer Management -> Software Distribution
    -> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
    Now you need to create 3 to 5 programs inside the package:
    1.  Name: Silverlight
       Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer. 
    The fact is the Silverlight installer is the same in both, so you only need one of them.)
       On the Environment tab:  Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
       On the Advanced tab:  Suppress program notifications
       All other options leave default.
    2.  Name:  Visual C++ x86
        Command Line:  x86\vcredist_x86.exe /q
       On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
       Environment and Advanced tabs:  same as Silverlight
       (If you have only x64 clients in your environment, change all x86 references to x64.  If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
    3.  Name:  Lync x86
        Command Line:  msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync"  (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
        Requirements, Environment, and Advanced tabs:  Same as with Visual C++ and Silverlight
        (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
    Now you need to make the Task Sequence.  Go to Computer Management -> Operating System Deployment -> Task Sequences.  Under the Actions pane, click New -> Task Sequence.  In the Create a New Task Sequence dialog, choose "create a
    new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
    The task sequence will have up to 12 steps in it.  I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
    Prereqs Phase:
    These are the easiest of the steps to do.  Highlight the task sequence and then in the Actions pane, click Edit.
    1.  Click Add -> General -> Install Software.  Name: "Install Microsoft Silverlight".  Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
    2.  Add -> General -> Install Software.  Name: "Install Microsoft Visual C++ 2008 x86".  Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
    As before, if you're an all-x64 environment, replace the x86 references with x64.  If you have a mixed environment, repeat step 2, replacing x86 with x64.
    3.  Add -> General -> Run Command Line.  Name: "Enable Lync Installation".  This step gets around the UseMSIForLyncInstallation registry requirement.  The Lync client MSI simply looks for the presence of this key when it runs, so
    we'll inject it into the registry now and it doesn't require a reboot or anything.  It just has to be there before the client MSI starts.
    Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
    Uninstall OCS Phase:
    This part consists of up to 6 Run Command Line steps.  (Add -> General -> Run Command Line)
    4.  Name: "Terminate Communicator".  Command Line: "taskkill /f /im communicator.exe".  On the Options page, check the box next to "Continue on error".  This will terminate the Communicator process if it's running, and if it's not, it'll
    ignore the error.
    5.  Name: "Terminate Outlook".  Command Line: "taskkill /f /im OUTLOOK.exe".  Check the "Continue on error" on the Options page here too.  Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
    because components are in use.
    (NOTE:  If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps.  I didn't run into
    this in my environment, though.  Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
    6.  Name: "Uninstall Microsoft Office Communicator 2007".  Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page:  Add Condition ->  Installed Software -> Browse to the
    Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
    7.  Name:  "Uninstall Microsoft Office Communicator 2007 R2".  Command Line:  "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart".  On the Options page:  Add Condition -> Installed Software ->
    Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
    SIDEBAR
    OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence.  I found out after I'd been deploying for a while that a tech in one of our remote
    offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there.  So, at first I just had our Help
    Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence.  Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
    and 7.  All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions.  This is part of how Windows knows that
    Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
    The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code.  This means that if I didn't have step
    6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong.  Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
    of the R2 client.  So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine.  If it was present, it uninstalled it and then skipped over the R2 step.  If non-R2 was not present,
    it skipped that step and instead uninstalled any version of the R2 client.  It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there.  What if neither is on the
    machine?  Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem.  It was assumed that the machines had some version of Communicator on them.
    8.  Name:  "Uninstall Conferencing Add-In for Outlook".  Command Line:  "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition ->
    Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    9.  Name:  "Uninstall Live Meeting 2007".  Command Line:  "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
    -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    Install Lync phase:
    Now, finally the main event, and it's pretty simple:
    10.  Click Add -> General -> Install Software.  Name: "Install Microsoft Lync 2010 x86".  Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program.  As before, if you
    only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
    And the task sequence is done!  The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement.  Go get a beer!
    Some final notes to keep in mind:
    1.  You can't make a task sequence totally silent...easily.  Users will get balloon notifications that an application is available to install.  The notifications cannot be suppressed through the GUI.  I've found scripts that supposedly
    hack the advertisement to make it be silent, but neither of them worked for me.  It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade.  The task sequence will appear
    in the "Add/Remove Programs" or "Programs and Features" Control Panel.  You can still do mandatory assignments to force the install to happen, you just can't make it totally silent.  On the plus side, the user shouldn't have to reboot at any point
    during or after the install!
    2.  In the advertisement setup, you can optionally show the task sequence progress.  I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress.  This means instead of seeing
    5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
    3.  One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete.  The user either had to start the client manually or just let it start on its own at the next logon.  However,
    while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
    tab, set it to "Run with user's rights" "only when a user is logged on".
    4.  My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
    and it would fail.  Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first.  It ran much more reliably this way.
    5.  For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
    then fail.  I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
    doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
    I hope this helps some of you SCCM and Lync admins out there!

    On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook.  Here's a list of the ones I found in the machines on my network:
    {987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
    {2BB9B2F5-79E7-4220-B903-22E849100547}
    {13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
    {C5586971-E3A9-432A-93B7-D1D0EF076764}
    I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

  • Problem with SMS_NOTIFICATION_SERVER

    Hallo Guys and gals
    I am having some problems with SMS_NOTIFICATION_SERVER, and i would like to know if anyone has any pointers onto where to look for a solution.
    This problem isn't one i have seen before.
    What i have done so far in regards to troubleshooting:
    If i look into the Monitoring log in "System Status" - "Component status", i get these errors:
    Notification Server on "Servername" failed to initialize. The operating system reported error 2147943458: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
    Possible cause: Failed to initialize with error code -2147023838.
    To help identify the problem, see the bgbserver.log on the management point "Servername".
    the error: -2147023838 Means:
    The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
    If i look into the "bgbserver.log" i get these errors:
    Error: Failed to create BgbServerController instance 80070422 SMS_NOTIFICATION_SERVER 1/14/2014 1:16:44 PM 4436 (0x1154)
    Failed to initialize BGB server. Wait 300 seconds to do initialization again SMS_NOTIFICATION_SERVER 1/14/2014 1:16:44 PM 4436 (0x1154)
    It doesn't look like i get any errors in the bgbmgr.log, this log has:
    Wait for events timed out after 60 seconds. SMS_NOTIFICATION_MANAGER 1/14/2014 1:21:51 PM 4516 (0x11A4)
    BgbManager is waiting for file and registry change notification or timeout after 60 seconds SMS_NOTIFICATION_MANAGER 1/14/2014 1:21:51 PM 4516 (0x11A4)
    in the logfile so far.
    if i look at the bgbsetup.log in the logfiles on the MP i don't see anything than, installation was successful, also Successfully configured BGB server applikation.
    I have no clue onto where to start my troubleshooting, also not if i can disregard this problem, as to my knowledge the BGB Server is related to push of the native policies functionality which was added in SP1.
    I am looking forward hearing from you Guys.
    Kind Regards
    Morten Leth

    Hi,
    I have the exact same problem as you Morten. I have searched for an answear, but come up empty. Anyone got any idea of what's wrong would be much appreciated. 
    Did you ever manage to solve the problem Morten?
    The log in the console says this:
    "Notification Server on xxx-sccm.xx.local failed to initialize. The operating system reported error 2147943458: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. 
    Possible cause: Failed to initialize with error code -2147023838.
    To help identify the problem, see the bgbserver.log on the management point hfs-sccm.hf.local."
    And when looking in the bgbserver.log, the following shows -  over and over again:
    "Error: Failed to create BgbServerController instance 80070422
    Failed to initialize BGB server. Wait 300 seconds to do initialization again"
    This is on a newly installed SCCM 2012 R2, on a Server 2012 R2.
    Kind Regards
    Mathias

  • Problem with App-V 5 in Xenapp 6.5 Feature Pack 2 /PVS Server 7.1 Environment

    Hi I hope someone can help me. We are pretty desperate right now.
    At e customer of mine we are Using App-V 5 SP2 RDS Client together with a Xenapp 6.5 Feature Pack 2 /PVS Server 7.1 Environment.
    The Golden Image for PVS gets built with SCCM 2007. We “Install” the App-V Packages local with Powershell with e Install Wrapper.
    The Wrapper uses for Example the following command to “install” the Package during the Task Sequence.
    Add-AppVClientPackage -Path "C:\_SMSTaskSequence\Packages\I010012B\x86-GE\001\Biella-Dominalprint(V)-2.0.appv" -DynamicDeploymentConfiguration "C:\_SMSTaskSequence\Packages\I010012B\x86-GE\001\Biella-Dominalprint(V)-2.0_DeploymentConfig.xml"
    | Publish-AppvClientPackage -Global | Mount-AppvClientPackage -Verbose >C:\Windows\Logs\Install\Biella-Dominalprint(V)-2.0_001.LOG
    The Package was Sequenced with SP1 Sequencer.
    The Package contains e SystemX86 folder
    C:\ProgramData\App-V\5D8F5879-923B-4401-BE13-F6E120F6569C\83FF2A00-5D2A-4A3B-82FD-3238D786BEE3\Root\VFS\SystemX86
    In This Folder are a few Files. One of them is the tdbg5.ocx
    The Package works without a Problem after the Installation of the Server has finished.
    But when the Citrix Department does there Magic with PVS and they provision the VHD to another Server the Package is no longer Working. When we start the App we get an Error that it is Missing the tdbg5.ocx
    But when I Use ACDC 2.0 to start the App or modify the Shortcut with the command /appvve: 5D8F5879-923B-4401-BE13-F6E120F6569C_83FF2A00-5D2A-4A3B-82FD-3238D786BEE3 it is working. Also when I remove the Package with Powershell from the provisioned Server
    and reinstall it again it is working Again.
    We have this Problem with two other Apps and both of them have files in the Root\VFS\SystemX86 Folder.
    We also have e Virtualized Java Package. We have a Shortcut like this:
    C:\ProgramData\App-V\1A971C0F-1C0F-430F-A2E2-2DF8487E6FF0\80A50994-7B30-4FC3-9DA4-1CE8B979B337\Root\VFS\ProgramFilesX86\Java\jre1.6.0.38\bin\javaws.exe
    http://whatever.ch/zpv/webstart/zpv-prod.jnlp
    If I start that link on the provisioned Sever Java Launches but it’s not downloading the App to the Cache. But also here it works perfect after the installation with SCCM, and it also works when I remove the package on the provisioned Sever and “install”
    it again with Powershell. But here the /appvve workaround doesn’t work.
    I know that we should ask that in the Citrix forums, the Citrix department of the Customer is opening a Case with Citrix and one with MS Support.  But we are I a big hurry because the customer needs to start testing the Apps, because they need to start
    the pilot Test very soon. So I hoped that someone in the community can help me out with this.
    Thank you for your answers
    Pascal

    Another alternative, if  you dont want to use the Shared Content Store, is to have your PackageInstallationRoot pointing to a non-provisioned disk (non-PVS).  In our environment we had the same exact issue.  Each of our Citrix servers have
    a D drive thats non-provisioned that we use for Logs.  Once I pointed the PackageInstallationRoot over to this location everything started working.   The key here is to have a script run at server startup that deletes the PackageInstallationRoot
    since the provisioned non-persistent disk will reboot to a fresh image each time.   This way you wont end up with stale content out there as applications are updated and/or removed. 
    There are other things that also have to happen for this to work in these types of environments (related to roaming profile exclusions) that I can provide to you if you need them.  
    Let me know if you want/need more details.

Maybe you are looking for

  • Internet Sharing for PPC and Intel based Macs

    I have OSX 10.4 Server running with NAT and DHCP enabled. The internet is accessed through a wired connection, and 2 Powerbooks(PPC based) and an Intel iMac and MacBook connected to the server via Airport. The wireless signal is WEP protected, and th

  • Flash crashes when opening certain file

    Hey Guys, I need some big help here...I have been working on the same file for the past several weeks and now when I open it, flash crashes. I have tried opening it on multiple systems with different operating systems. Nothing is working. Any ideas?

  • Query read / cache modes are set in BW

    Hi Experts, What is query read / cache modes are set in BW in order to improve the query performance? Thanks Rohan

  • Acrobat Pro 8 Registration Error

    I keep getting a message that I need to register my version of Acrobat when I try to print to Adobe to create a PDF file. I go to the Help tab, click on register and it shows I am registered. Only after I repair the installation will it work for a da

  • LIV for reversal document

    Hi, In LIV, if GR based IV is flagged system should not allow to post invoice upto completion of GR. This is happening if you are doing the invoice posting before doing any GR, but if we do the GR first and reversed(102) it on same day or later day t