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_SupConfigOOB

Since 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

Similar Messages

Automatic Install of Endpoint Protection fails on windows 8.1 clients with SCCM 2012 R2

Running SCCM 2012 R2 and deploying CM clients and Endpoint Protection via software updates. CM client and EP install fine on Windows 7 clients. CM client installs fine but endpoint protection fails on Windows 8.1 clients with the following from the
endpoint protection agent log:
<![LOG[Create Process Command line: "C:\Windows\ccmsetup\SCEPInstall.exe" /s /q /policy "C:\Windows\CCM\EPAMPolicy.xml".]LOG]!><time="12:22:02.560+240" date="08-13-2014" component="EndpointProtectionAgent"
context="" type="1" thread="4260" file="epagentutil.cpp:607">
<![LOG[Detail error message is : [EppSetupResult]
HRESULT=0x80070643
Description=Cannot complete the System Center Endpoint Protection installation. An error has prevented the System Center Endpoint Protection setup wizard from completing successfully. Please restart your computer and try again. Error code:0x80070643. Fatal
error during installation.
So on the win8.1 client I run the above command line manually in a command window and receive Access is denied. Then I run the same command in an elevated command window and EP installs fine. Does this have something to do with why the automatic
EP client install fails with the 0x80070643 error code? If so, what is the fix?

Hi,
Try uninstalling any other security software.
For more information, please review the link below:
I‘m getting an error code from my Microsoft security software
http://www.microsoft.com/security/portal/mmpc/help/errorcodes.aspx
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.

SCCM fails to deploy Patches to client with in the maintenance windows.

Hi,
I am new to Patchng through SCCM just 7 months of experience.
I deploy the patches regular month basis as microsoft release the patches every month. till now the patch deployment was happening smoothly, but from last month i am facing issue like the SCCM failed to push the patches with in the provided maintenance window.
even if the maintenance window over client will not get install.
i have checked the enforcement status report for the same collection which i deployed, the status is always downloading updtaes.
We have collection called Workstation and servers, both the collections compliance is less like 20% or lesser than that.
Arround 800 Workstations deployed and given deadline 10 days. with suppressed reboot.
Arround 70 Servers deployed with with automatic reboot via Maintenance window.
deadline to install is 1 hour ahead of maintenance window.
It would be great if any one suggest the solution to make software update deployment through SCCM with in the maintenance window.

Vista is not a supported OS for Acrobat XI Pro.

Deploy upk client with sccm

hello guys!
i need help
how to deploy upk client 11.1.0.1 with sccm?
thanks

If you want to deploy lync by SCCM, you may utilize config.xml to do that. All the things you want to configure, you may find it can be achieved in config.xml
Run the install by using the following command line:
<path>\setup.exe /config <path>\config.xml
http://technet.microsoft.com/en-us/library/jj204651.aspx
How to deploy application by SCCM.
http://technet.microsoft.com/en-us/library/gg682082.aspx
Juke Chou
TechNet Community Support

Windows 2012 to Windows 2012 R2 Inplace with Sharepoint Foundation 2010 SP2 (4.0.7116.5000)

I found than Inplace update from 2012 to 2012 R2 are supported. I also found 2012 R2 will support SharePoint Foudation 2010 with SP2 (4.0.7116.5000).
But I cannot find if we perform an Inplace update from a Windows 2012 Server running SharePoint 2010 (Sp2) to R2 will be successful.
As anyone done that?
Thanks.
Real
Réal Doré

Hi ,
On Windows Server 2012 R2, Microsoft supports only the SharePoint Server 2010 SP2 slipstream media configuration and not the RTM version of that configuration. For full SharePoint functionality and support, you must have the February 2014 cumulative update
(CU) or a later CU installed.
Additionally, only a new SharePoint Server 2010 SP2 slipstream installation that has the February 2014 CU or a later CU installed is supported on Windows Server 2012 R2. Microsoft
does not support a Windows in-place upgrade for this scenario.
For your scenario, I suggest you create a new SharePoint Foundation 2010 with SP2 on Windows Server 2012 R2, then migrate the content to new SharePoint 2010.
More information, please refer to the link:
http://support.microsoft.com/kb/2724471/en-us
I hope this helps.
Thanks,
Wendy
Forum Support
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]
Wendy Li
TechNet Community Support

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

DPM 2012 R2, Windows 2012 R2, and "stop" VM during backup

I did upgrade
DPM 2012 SP1 to 2012
R2.
DMP backup the server with Hyper-V
machines, windows / linux.
The previous version of Windows, as
did backup via partition shapshot
not stop its operation.
Current unfortunately it does!
During backup closes all connections
to the virtual machine, start the
copy and return connections.
Hyper-V also shows the
beginning of a new machine to count
on time as if they held the
restart (even though it was not).
As every change / off?
Going back to the previous version?
Backup Group I created again
- does not help.

"We are looking for what is
the procedure for checking why
the DPM wants
to do only
offline backup"
Yes that is why I asked what do you see in your "Windows Server Backup" from the Hyper-V host. Did
you do an update at the Hyper-V Hosts? Could you update the Hyper-V integration tools in your Virtual Machine?
What guest system is used in your windows virtual machine? If there a Windows Server 2008 R2 (with installed SP1) or a windows server 2012 you should try to update the integration tools at this machine first. When updated is done, try to backup online again.

Best practices for mass reimaging? Having unmanaged duplicate clients with mismatched Resource IDs. (2012 R2)

We reimage about 5000-8000 clients each summer. Last summer we were still at RTM, but have since moved on to R2. We build images (Win7 SP1) in vsphere and capture via capture media TS. Last year's image didn't get SCCM client uninstalled prior to capture
so we would have random issues with computers going to unmanaged status and some that would show up without a client cert. To avoid this issue we stripped the client out prior to capture this year.
I believe this is how we handled the reimage process last year as well, but I am not positive on that. We were also dealing with a lot of new laptops last summer, where as they obviously have existing records this summer. Since SCCM replaces the wired MAC
address with the wireless MAC (laptops) we can't just toss these into an OSD collection because it won't pickup the OSD advertisement / PXE. (Is there any workaround for this?) Since this is the case, we are blowing away each client's AD account and DDR in
SCCM, then doing mass import of hostname and wired MAC into SCCM, dumping them into the appropriate OSD collection, and they image unless they happen to pickup last year's PXE deployment that first has to be cleared, or unless they had a motherboard replaced
and our MAC database didn't get updated. We did the mass import a week ago and the manual entries are listed with hostname and MAC and entry date of 7/9/2014. This week we started imaging. Almost immediately after reimaging (at which time the AD record is
created upon rejoining domain) we see a second account show up in SCCM from AD Discovery with dates of 7/14/2014 and 7/15/2014. Neither account is managed or shows that SCCM client is installed, but it shows a site code.
The manual entry lists an agent name, agent site, wired MAC, name, NetBIOS name, Resource ID of 167xxxxx, assigned site, and CCM GUID.
The AD Discovery record shows agent name, agent site, domain, IPv4 and IPv6 addresses, name, NetBIOS name, primary group ID, domain, Resource ID of 20971xxxxx, resource name and type, SID, assigned sites, container name, UAC, etc.
Why won't these records merge and show up as being properly managed? I am not yet sure if they fix themselves after one record or the other is deleted. Obviously this process isn't working well and it removes the clients from their direct membership collections
and AD groups. I'd think that all of this could be avoided if we just had the wired MAC persist in the DDR.

Last year's image didn't get SCCM client uninstalled prior to capture so we would have random issues with computers going to unmanaged status and some that would show up without a client cert. To avoid this issue we stripped the client out prior to capture.
There is no reason or need to do this. There is no correlation between the two as long as the client agent was properly prepared (which does happen with capture media although you should strongly consider using a build and capture task sequence). Clients
are perfectly capable of living within an image -- I do it all the time and it is a common practice.
Since SCCM replaces the wired MAC address with the wireless MAC (laptops) we can't just toss these into an OSD collection because it won't pickup the OSD advertisement / PXE. (Is there any workaround for this?)
This is not correct and thus also unnecessary as ConfigMgr will use the MAC Address *or* the SMSBIOS GUID of the system to determine targeting during OSD. The SMBIOS GUID is an immutable unique ID set by the OEM that is part of the resource record in ConfigMgr
also.
Jason | http://blog.configmgrftw.com

Guest two node Failover Cluster with SAS HBA and Windows 2012 R1

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George
1) Update to R2 and use shared VHDX which is a better way to go. See:
Shared VHDX
http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-feature-in-windows-server-2012-r2.aspx
Clustering
Options
http://blogs.technet.com/b/josebda/archive/2013/07/31/windows-server-2012-r2-storage-step-by-step-with-storage-spaces-smb-scale-out-and-shared-vhdx-virtual.aspx
2) If you want to stick with non-R2 (which is a BAD idea b/c tons of reasons) you can spawn an iSCSI target on top of your storage, make it clustered and make it provide LUs to your guest VMs. See:
iSCSI Target in Failover
http://technet.microsoft.com/en-us/library/gg232632(v=ws.10).aspx
iSCSI Target Failover Step-by-Step
http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
3) Use third-party software providing clustered storage (active-active) out-of-box.
I would strongly recommend to upgrade to R2 and use shared VHDX.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

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.

SCEP 2012 Client in Windows 8 / 2012 - in Windows 2008 Domain- Not Syncing -/ Not Compatiable

Dear All ,
With lots of Hardship I had installed SCEp 2012 in Windows 2012 Virtual machine in WIndows 2008 Domain.
SCCM 2012 Server in Windows 2008 Server with Sql 2008 was - performing well and there was no issues until our COmpany planned to Convert the Windows 2008 Server to Windows 2012 Server ( AD is 2008)
WSUS is not Fully synching with SCCM 2012 ( previously it was )
Software Updates not pushing properly and to top all the SCEP client is not compatible with win 8.1 pro or win 2012 server
Error: Failed to download content id 16787046. Error: Access is denied.
Package:
Success: The software updates were placed in the existing package:
• Deployment Package(JUN2014)
Software updates that will be downloaded from the internet
Error: Update for Forefront Endpoint Protection 2010 Client - 4.1.522.0 (KB2780435)
Errors
Failed to download content id 16787046. Error: Access is denied.
Language Selection:
English
But the service account has full access - administrative rights and the administrator of the system
please advise on this

Hi,
All the software updates downloaded failed?
Are there any errors in PatchDownloader.log? If you use Automatic deployment rule, please also check ruleengine.log.
Please add the account with Full rights to the source share (both NTFS and Share permissions) where the Deployment Package is located.
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.

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?

Connect Oracle 9 client from windows 2012 server to 9.0 oracle database

I have windows 2012 64 bit with installed oracle 9.0 32 bit client
and i want to connect to oracle 9.0 64 bit server installed on windows 2003 R2 64 bit
Is it possible to make this connection because when i have tried to connect received this error ORA-06413 connection is not open

942609 wrote:
I know that oracle client 9.2.0 is too old but company about i work have tests which run on this systemIf you are stuck using antiquated versions of software, the company really ought to stick to antiquated versions of the operating system as well. Trying to combine versions of the Oracle client that weren't even certified on Windows 2003 with a bleeding edge Windows 2012 system is a recipe for pain and suffering. Even if you appear to get things working, there are any number of bugs that will likely crop up over time due to the massive version incompatibility.
If i understood right i can't make connection between oracle 9.2.0 32 bit client installed on windows 2012 to connect to oracle server 10 i?As others have pointed out, you probably can though you'll need to change the firewall rules. As others have stated, the firewall changes you'll need to make should probably be the same for a 9.2 client and a 10.2 client. But if you're determined to work with highly unsupported combinations of software, you're likely to have to embrace the idea that you're going to be blazing some new trails and that you'll have to spend a decent amount of time debugging issues that arise from your very unique combination.
Justin

SCCM 2012 SP1 + WSUS + Server 2012 + SQL Server 2012

Hi all;
I installed SCCM 2012 with Sp1 for my site server and everything is going well.. And than i installed the WSUS role on my Windows Server 2012 and SCCM 2012 SP1 it gave an error message which is "Fatal Error: The schema version of the database is from a newer
version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database." My database server is SQL Server 2012... Do you know any pathc for WSUS or SQL Server 2012 doesnt support WSUS yet???
Thank You...
MCT

Normally if you are going to install SCCM 2012 SP1 +Windows 2012 with SQL 2012, Then you better use the SQL 2012 sp1.
also when you are installing the WSUS version 6.2 which come with server 2012 make sure you leave the default settings as it is. it shows in the below article.
also when you are giving the path to save the WSUS contents make sure the drive you going to create the wsus folder and the place where you going to download the updates is having free disk space and its formatted with the NTFS volume. Also the service account
you are using for this configuration should have the admin rights to the location of the wsus folder you going to create,
Thanks
Hasitha

Fortinet configuration with SCCM - just looking for experiences with it.

Just looking for experiences with Fortinet SSL gateway and managing clients with SCCM with it. I'm planning on building a lab area and selling management the idea of using Windows Defender and managing the 700 remote clients we have with our SCCM 2k7
R2 setup on Windows 7.
So if anyone has any experiences it would be handy. Or white papers would be awesome.
Trying to figure out an SSL gateway product with a path of least resistance that isn't Citrix.

Yes, I know this is an old post, but I’m trying to clean them up.
You will get more responses from Fortinet forums.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

AMT 3.2.10 Clients with SCCM 2012 on Windows 2012

Similar Messages

Maybe you are looking for