Using CAU with SCCM
We're currently using SCCM to manage the updates of computers in our domain. However we have a failover cluster that we placed in an SCCM group that allows us to manually apply the updates. We would like to leverage CAU to allow the cluster to
self-update. Being that SCCM offers the updates through Software Center and not Windows Update CAU in turn does not see these updates. Is there a way that we can configure SCCM and CAU to work together so that SCCM serves the updates to the cluster
and CAU applies them? Everything I've been reading says that this would require a plug-in but that no such plug-n exists yet.
Any help on this would be much appreciated.
Thanks,
Jake
I was just under the impression that there is some level of use between the two that can be accomplished from reading forum discussions and the CAU FAQ on Technet which this is from.
Can CAU work well with System Center Configuration Manager?
Yes. A server administrator should consider the following levels of interoperability between System Center Configuration Manager and CAU:
Coexistence CAU is a tool that coordinates software updates on a cluster node, and Configuration Manager also performs server software updates. It is important
to configure these tools so that they do not have overlapping coverage of the same servers in any data-center deployment. This ensures that the objective behind using CAU is not inadvertently defeated, because Configuration Manager-driven updating does not
incorporate cluster awareness.
Leverage CAU and Configuration Manager can work together to deliver synergistic value. By using the public plug-in interface architecture in CAU, Configuration
Manager can leverage the cluster awareness of CAU. This allows a customer who already has Configuration Manager deployed to use the cluster awareness capabilities of CAU while taking advantage of the Configuration Manager infrastructure, such as distribution
points, approvals, and the Configuration console. For more information, see Cluster-Aware Updating Plug-in Reference.
Similar Messages
-
Adobe Flash 17.0.0.134 and SCUP with SCCM
Not specifically an SCCM issue I know, but unfortunately the Adobe forums are very sleepy.
Basically I'm just wondering if any one using SCUP with SCCM to update Adobe Flash, and if they've noticed there's no sign of the latest Internet Explorer or Plugin version: 17.0.0.134 ?
The update process has worked fine for me until now.Hi,
Glad to hear that and thanks for your feedback.
Have a nice day.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] -
Hi,
I heard some promote use of "Terminal Services(RDS)", rather than App-V application with SCCM 2012 even if you have SCCM licens. The reason you dont need to repackage\test the application on an client OS...
I don't agree and I have not Heard this Before, just that you use TS for some scenario.
Or is it more likely that "Terminal Services(RDS)", take over the applikation administration?
/SaiTechSurely this all depends on your environment. There's nothing wrong with creating RemoteApps to push to client devices. Maybe you have an environment where RDS is widely used.
Why not leverage both solutions and target App-V's at RDS servers and then create App-V based RemoteApps that users can run at home as part of a home working solution via RDWeb.
Creating apps via RDS will be an admin overhead yes but then so is creating App-V packages in SCCM.
I don't agree with the arguement re: 'you dont need to repackage\test the application on an client OS...' as
App-V allows you to run on multple O/S types.
To be honest both technologies have their pros and cons.
Cheers
Paul | sccmentor.wordpress.com -
Hi,
how to find using SCCM SQL query, application deployed on win 7 machines with SCCM 2012 server or user/technician installed manually. Please let me know.Thanks, is it not possible via any script also?
Like Torsten said, how can you tell the difference between CM12 installed applications and locally installed? Once you can answer that, then you can write report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ -
In the past I have always created a deployment with sccm and installed firefox.exe with the /s switch from the command line what is the new switch for silent installation ?
hello, have you tried it with the full installers that are available at https://www.mozilla.org/firefox/all yet?
-
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.
RyanWindows 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. -
Unable to install MBAM 2.5 with SCCM integration on named SQL instance
Hi,
in production i am installing MBAM 2.5 with SCCM integration but during the installation it asks for the SCCM reporting services point and which it is unable to recognize.
whereas in my lab environment i have default SQL instance which has reporting installed, in that case it works fine.
can someone let me know why the issue is coming?
in the event log the issue is : Description = "user domain\username is not able to get the lock at this time.Error:0x40480732"For the integration part, You need to install the MBAM SCCM Integration feature on SCCM server. For compliance reporting in integration, MBAM uses the Reporting service point for SCCM.
When installing the SCCM integration feature, you need to provide the name of the reporting Server where Reporting Service point role is installed for SCCM. But it does not provides any option for the instance but for the Server only. We have two instances
for SQL. One for CAS and other for Primary site. We need to run the installer on CAS and hence need to connect to the SQL instance for CAS.
We have also tried with the powershell commands but it is not working either.
Is there any way to install MBAM integration feature on a SQL instance. As far as I know, it automatically picks the instance but not happening for me.
Gaurav Ranjan -
Deploy UDI Windows 10 with SCCM 2012 R2 and MDT 2013 Update 1
Hi,
Trying use "User-Driven Installation" with
SCCM 2012
R2 CU4 and MDT
2013 Update 1 for deploy Windows
10.
Created MDT Task Sequences with
template "Client Task sequence"
and Deployment Method "User-Driven Installation".
When I try to deploy I have error like:
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Part smsts.log
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Expand a string: WinPEandFullOS TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 22.04.2015 11:36:57 1160 (0x0488)
[ smsswd.exe ] InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
PackageID = '' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
BaseVar = '', ContinueOnError='' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
SwdAction = '0001' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Set command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Working dir 'not set' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Executing command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft (R) Windows Script Host Version 5.12 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft Deployment Toolkit version: 6.3.8216.1000 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the action: Error in the task sequence.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionRetCode=5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 22.04.2015 11:36:57 1160 (0x0488)
Clear local default environment TSManager 22.04.2015 11:36:57 1160 (0x0488)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 22.04.2015 11:36:57 1160 (0x0488)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
The command completed successfully. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
Successfully launched command shell. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)MDT Updates for Windows 10 Technical Preview Build 10041
Если Вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку "Предложить как ответ" или "Пометить как ответ".
http://zalozny.com.ua -
How to uninstall Adobe Reader 9.2 with SCCM
Hello, I am trying to create an uninstall packed for Adobe Reader 9.2 and push it out to the clients with SCCM (System Center Configuration Manager).
But the main problem I am having is that after creating the package, on the left side I drill down to the following folder "Software Distribution/Packages/Adobe Acrobat 9.2 Uninstall/Programs". Then I right click on it and choose "new then program".
Then I type the name and in the 3rd box I can type a command line. So I typically use the following. msiexec.exe /uninstall AcroRead.msi
Then I distribute that package to my client machine in hopes that it will uninstall and nothing happens. I have it set to advertise after about 2-3 minutes.
I think my problem lies with the command line. Probably not using the right switches. I basically want it to do a silent uninstall and reboot the machines
after it is done. I want pretty much no user interaction what-so-ever.
Any help with this is appreciated. Attached is a screen shot of what I am talking about talking about.The command we're using is msiexec /x {AC76BA86-7AD7-1033-7B44-A92000000001} /qn
Give that a try? -
SQL Server reporting (SSRS) with SCCM. Language issue - how to change it?
My SCCM 2012 R2 server is setup on a Windows 2012 R2 server (English) but has non-English language pack installed.
I have the server working great with SCCM 2012 R2 working in English.
The reporting has turned out to be a bit of an issue as it is displaying the paths in the other language.
For example if I browse to http://servername/ReportServer and click to view the available reports the links are all non-English.
Also, if I go to the ConfigMgr console -> Monitoring -> Reports the names appear in English but if I click on any of them to view their properties and go to the security tab I can see the path is not English.
I want to, for the sake of some of the people that will be viewing/using the reports, change it into English.
Is there any relatively painless way to do this?
Changing the language preferences in Internet Explorer does not affect it as these appear to be hard coded.
Appreciate any advice. Thank you.Thank you. I had previously seen that page but unfortunately it did not resolve my issue.
It is quite frustrating as I can see the actual folders on my server in English (C:\Program Files\SMS_SRSRP\Reports) yet in the browser the folder names and URLs appear not in English.
Also looking at Reporting Services Configuration Manager it does not show any option to configure this. Arg! -
AMT 3.2.10 Clients with SCCM 2012 on Windows 2012
Hey
I have a couple of HP dc7800 computers with Intel's AMT/vPro that I'd like to provision with SCCM 2012. The installed firmware version is 3.2.10 which is a supported version according to the documentation [1]. Provisioning of newer clients (5.2.x upwards)
is successful, so I can rule out all the usual suspects like the provisioning certificate from GoDaddy, our internal CA, DHCP options, etc. Provisioning with SCCM 2007 of both 3.2.x and 5.x AMT devices is also still successful.
The amtopmgr.log repeatedly shows the following entries:
Provision target is indicated with SMS resource id. (MachineId = 16777325 WS45.mydomain.ch)
Found valid basic machine property for machine id = 16777325.
Warning: Currently we don't support mutual auth. Change to TLS server auth mode.
The provision mode for device WS45.mydomain.ch is 1.
The IP addresses of the host WS45.mydomain.ch are x.x.x.x.
Root hash of provisioning certificate is 2796BAE63F1801E277261BA0D77770028F20EEE4.
Attempting to establish connection with target device using SOAP.
Create provisionHelper with (Hash: 74B7792EDBD64EBB01E2E3A0B27FAFA04C2D3BCB)
Set credential on provisionHelper...
Try to use provisioning account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioning account #0.
Try to use default factory account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using default factory account.
Try to use provisioned account (random generated password) to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioned account (random generated password).
Error: Device internal error. This may be caused by: 1. blabla...
Error: Can NOT establish connection with target device. (MachineId = 16777325)
After some investigation with Wireshark, I've found out that SCCM tries connect with TLSv1 to the AMT device. The response from the device is immediately an SSL alert (internal error). Using OpenSSL, I could connect to the device if I explicitly told it
to use SSLv3. This leads me to believe that the 3.2.x firmware cannot handle TLSv1 correctly and SCCM never tries to connect with SSLv3 after a failure.
So the question is: How can I get SCCM 2012 to provision these devices?
Regards,
Ingo
[1]
http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigOOBSince no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ -
SCCM 2012 R2 coexist with SCCM 2007 - DPs issue
Hi all,
I have a SCCM 2012 R2 which coexists with SCCM 2007 and I'm not interested in a migration, but my question concerning the use of DPs. Is it possible for 2012 R2 clients to use a 2007 DPs, i.e. are there settings for a sort of compatibility? I've looked among
links, but most of them are related to migration.
Please advise,
DomenicoNo, you can only share a distribution point during a migration between a source and destination hierarchy (see also:
http://technet.microsoft.com/en-us/library/gg712275.aspx). Without a migration that's not possible.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
MBAM 2.0 with SCCM Integration: Recovery Audit Reports errors.
I have installed MBAM 2.0 with SCCM integration according to the following website:
http://myitforum.com/myitforumwp/2013/06/10/how-to-install-mbam-2-0-with-configmgr-integration/
Topology:
SCCM 2012
SCCM SQL Server
MBAM Server
MBAM SQL Server
Components installed:
Integration components on SCCM 2012 server
Compliance and Audit Reports on SCCM SQL Server
Recovery and Audit Databases on MBAM SQL Server
Self-Service and Administration Monitoring on MBAM Server
Everything is running correctly: SCCM sees compliance reports, keys are populating into the Recovery database. Self-service works correctly as tested.
However, the Recovery Audit Report in the /Helpdesk webpage reports an error:
"Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection)
Browsing to the /Reports page on the MBAM SQL server (with reporting) yields an empty page.
If I install the Audit and Compliance reports onto the MBAM SQL server, those populate (but are empty, as SCCM is handling that component), however, the Recovery Audit Report still yields the same error.
Ideas?
Thanks,
-PatrickYou can put the Audit Reports on the SSRS instance on SCCM Server. But it has its own limitations. What if you want to configure the encrypted configuration within the MBAM environment using SSL certificate. In that case you have to take special
care while using the SSL certificate for configuring the reporting Point as it has been also used by the SCCM.
Gaurav Ranjan
So, let me get this clear, I can install the Audit Reports onto the SRSS I am using for SCCM and not have to deploy an SRSS instance elsewhere? The SSL certificate detail is not an issue. I am desperately trying to avoid yet another instance of
SRSS.
Thanks -
How to use CAU in 2012R2 to install the specific kind of update
Hi all,
Can any body heklp me how to use CAU to install the specifc kind of update, such only insatll hotfix but not the function update, Thanks.
Hi SpaceTime_L,
The plug-in Microsoft.HotfixPlugin can be used to apply Microsoft limited distribution release (LDR) updates (also called hotfixes, and formerly called QFEs) that you download
independently to address specific Microsoft software issues.
Microsoft.WindowsUpdatePlugin
Communicates with the Windows Update Agent on each failover cluster node to apply updates that are needed for the Microsoft products that are running on each node.
Installs cluster updates directly from Windows Update or Microsoft Update, or from an on-premises Windows Server Update Services (WSUS) server.
nstalls only selected, general distribution release (GDR) updates. By default, the plug-in applies only important software updates.
The related KB:
How CAU Plug-ins Work
https://technet.microsoft.com/en-us/library/847b571b-12b3-473c-953f-75a5a1f51333#BKMK_ACL
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Maybe you are looking for
-
Macbook Pro trackpad and keyboard freezes after attempting sleep mode
I bought this computer on April 2008. It has the latest OS X 10.5.6 and it did not accept the trackpad firmware. I tried to install and the software said "this computer does not need this update". This has been happening a lot when I am using Skype w
-
24" iMac with Bose Campanion III Speakers....strange noise?
Dear All.. Not sure if I am posting in the right place, but perhaps someone can help me anyway. I have an iMac which has Bose Companion III speakers plugged in to it. I love them....absolutely amazing sounds. So much so that my neighbour has been dow
-
My computer froze during match initial formatting. Now some songs are uploaded others are "greyed out." If I go song by song, I can update match. How can I do this all at once and also update album art?
-
Hi all, i've understood the bursting problem i'he had since my first tests on it, i've posted a couple of threads but without any results. Now i've found the reason and it is very very strange. As i wrote in my threads my test was made on a single (a
-
Will a MacBook Pro case from 2009 fit my new MacBook Pro?
So I just bought a new 13" MacBook Pro w/o retina display from Apple and there's a case I'm looking to buy for a 13" MacBook Pro w/o retina display, but the case was made in 2009. Are there any structural differences between the two? Can I still use