Deploy FEP definitions with WSUS without SCCM.

Morning,
Possibly a silly question but better to find out now than after configuring a VM with WSUS and finding out it won't work.
One of our clients can't migrate from XP right now, to minimize risk we've denied their access to the internet on these machines. Now we are faced with FEP not being able to update anymore. I've looked up the IP adresses to allow them but they are many and
constantly changing.
WSUS could be an option for them but do we also need SCCM to deploy FEP definitions and updates via WSUS? I will find out myself how this works but I want to make sure it is possible.
Thanks ;)
I know Forefront Client Security definitions are in WSUS. FEP definitions should be available also. FEP 2010 is listed in the Proucts list in WSUS Products and Classifications. When using FCS definitions, I altered the frequency of WSUS checking with Microsoft
for updates. The frequency I use is one check early in the am, One at 8 am, one at 1 pm, and one at 4 pm.
So looks like all you have to do is choose that product in WSUS and sync. Let us know if the FEP product definitions get synced.
Hope this helps.

Similar Messages

Update deployment plan definition with WLST

Hello,
I would like to write a script in order to get the existing deployemnt plan of my deployed application (Deployement plan is yet modified, I don't want to use loadApplication). Then I would to update my deployement plan (update/add work manager constraints).
I can't find any WLST api to do that. The Weblogic console doesn't record the actions when I do it through the console.
I would like top the the same as this link http://download.oracle.com/docs/cd/E15051_01/wls/docs103/config_scripting/updateplan.html
But with a deploymenPlan got from the server and not from the filesystem
The only way I see is to use a Java parser un Jython to update the existing deployemnt plan and then, redeploy the application but This solution is very heavy in term of developpment. It should be more efficient when a built in parser
Could you please help me giving me some information about how to update deployement plans of a yet deployed application with WLST ?
Thank you !
C.

Thank you for answering.
In fact, I have found the solution for my use case according to the previous html link
The WLST plan seems to be accessible only by file system.
If your application is yet deployed with a deployment plan and you want to update this plan, you have to login on the admin server via WLST,get the application absolute path and the plan absoluth path :
cd ("AppDeployments/" + INTERNAL_APP_NAME)
appPath = cmo.getAbsoluteSourcePath()
planPath = cmo.getAbsolutePlanPath()and then, load the existing plan :
plan = loadApplication(appPath, planPath)after that, you can use the api described at the following link http://download.oracle.com/docs/cd/E15051_01/wls/docs103/config_scripting/updateplan.html to update the plan.
Then, you have to redeploy the application :
redeploy(APP_NAME)Thank you for helping !
C.

Error to Deploy Search Definition in PeopleSoft HCM 9.2

Hi Guys,
Today i'm trying configure SES with my Peoplesoft. When i try to deploy Search Definition. I got this error "
PeopleCode compile error (AddQueryFieldDefaultValueExpression is not a method of class CQRuntime. (2,52) ^ PPT) for program PTSF_FEED.SESFeedDataSource.OnExecute. (2,405)
A PeopleCode program for the specified reference failed to compile correctly for the indicated reason.
In Application Designer, open the referenced program and examine the PeopleCode to locate the cause of the error."
Any suggest for this problem ?
Thanks before for yours reply.

As stated in the following doc, this issue has been solved in PeopleTools 8.53.04 patch
E-SES: Problems Deploying Search Definition With PeopleTools 8.53 And Oracle SES 11.1.2.2.0 [ID 1558997.1]

Install IE10 and required security patches with WSUS with only 1 or 2 reboots

We are planning to deploy IE 10 with WSUS. Currently, it takes 1 reboot to apply IE 10 and 2 subsequent reboots to apply all the identified security patches for IE 10 via WSUS. We are under close scrutiny to limit the number of times that computers
must be rebooted to apply patches so that we don't impede our business function.
Is there anyway to deploy IE 10 and all required IE 10 security patches with WSUS with only a single or 2 reboots? As I understand WSUS already "packages" or "layers" patches in a manner to limit the number of reboots and that
various patches must be installed only after pre-requisite patches are identified as installed.
We are rolling out to a couple thousand machines and want to make the business impact as little as possible.
Any help would be appreciated.

and 2 subsequent reboots to apply all the identified security patches for IE 10 via WSUS.
I find this unusual. Exactly how did you determine this to be the case. Which updates are you actually deploying to an IE10 environment?
My investigation identifies that the only two updates are applicable to an IE10 (on Windows 7) environment. They are MS14-011 (KB290920), released Feb 2014, and MS14-056 (KB2987107), released Oct 2014. Since these two updates *CAN* be installed
concurrently, at worst these two updates installed concurrently would only trigger one reboot -- assuming they trigger a reboot at all.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

How to deploy LifeCycle Designer with SCCM

The company I work for has purchased Adobe LiveCycle Designer version 11. I'm trying to find out what parameters can be sent to the MSI file via Setup.exe. I'm mainly looking at how to pass the license key to the MSI so I can deploy this software with SCCM.

Hi,
As Gerry said, please test the command line to uninstall Office 365 without user interaction before using SCCM.
If this command line cannot work, you could get better support from Office forum.
http://social.technet.microsoft.com/Forums/office/en-US/home?forum=officeitpro
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.

Reinstall Corrupted WSUS without conflicting with SharePoint services, SBS 2008

My SBS server 2008 is a little complex but If someone can please advice me on below, it would be much appreciated....
My SBS server 2008 is a little complex but If someone can please advise me on
below, it would be much appreciated....<o:p></o:p>
SBS server 2008 had WSUS & SharePoint services running but the WSUS database
was corrupted. I have tried to fix WSUS database but failed to do so....<o:p></o:p>
I have used the option to "repair" WSUS through its Setup.exe file to do a
complete reinstall. The WSUS did uninstall parts of itself but was not
completely removed.....The service has been removed from the repair process...."Update services" folder remain.
I need to install WSUS services but I am not familiar with SharePoint...How would I
reinstall WSUS without conflicting with SharePoint??<o:p></o:p>
Any advice would help.<o:p></o:p>
Thanks,<o:p></o:p>
Andrew<o:p></o:p>

I hope you have already followed
http://technet.microsoft.com/en-us/library/dd443475(v=ws.10).aspx
To install WSUS, download WSUS 3.0 SP2 and install it
Create WSUS Group Policies :
http://blogs.technet.com/b/sbs/archive/2013/04/24/how-to-manually-create-the-sbs-2011-standard-and-wsus-group-policies-objects.aspx
Regards,
Mahesh Ramola

Disable Automatically Deleted Updates Download on SCCM 2012 with WSUS

Hi
I have SCCM 2012 SP1 with WSUS integrated, both are on the same server, I created a structure where I downloaded the updates:
D:\Wsus\HotfixWinX
D:\Wsus = The folder where I installed the WSUS role
HotfixWinX = The folder where I downloaded the hotfix
When I run "Synchronize Software Updates" the updates downloaded with a time of old age are eliminated automatically, have reviewed the log wsyncmgr and I found this:
My question is, how can I prevent updates and updates folders to be automatically deleted?
Thank you.

This is a fully automated process that only works for expired updates. Do keep in mind that after this specific message the updates still exist in the console. For a very good complete explanation, see:
http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Forefront Endpoint Protection Definitions Not Updated via SCCM (SCCM 2012 SP1)

Hi All
We have an issue of FEP definitions not updating correctly.
1. Clients getting definitions updates from the internet, not SCCM. Any solution?
2. Currently, we have around 20 workstations installed with FEP but having more than 7 different definitions versions within those. Waited for a couple of days but still not updating.. kind of random.
Any advice where to check or what is to be done?
Regards,
Xavier

(Assuming you are using ConfigMgr 2012)
Part of the Antimalware policy is the tab Definition Updates, in this tab you can define the update location(s). Also, in the normal client settings you can disable the client from going online for their initial definitions.
Make sure you are deploying the latest updates via ConfigMgr (either via an ADR, or a custom Software Update Group).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

WSUS vs SCCM SUP - What is the point of changing? Pros and Cons of both

Hi,
I have been using WSUS forever and have just made a very painful change over to SCCM 2012 SUP. In a room full of experienced WSUS users and facing a handover of SCCM SUP, I really need to have this question answered - What, if any, are the advantages of
SCCM2012 SUP over WSUS. It's certainly not ease of use, ease of implementation or understandability.
Even if i accept that yes, they are two different things now and i shouldn't think of SCCM as being like WSUS, I still have to compare and contrast, honestly, what they do and how they do it
WSUS is ridiculously easy in comparison to SUP. With WSUS, I install it, create some GPOs and assign to OUs. I create security groups and add the servers in scope to to thoise groups and those security groups to the policy. I have different groups set up
to keep separation of DCs and APP servers and SQL and SCCM and Antivirus servers and workstations
If needs be i have a text list of all my servers/workstations and can individually target using PSEXEC to run wuauclt on any number of clients. It works great and is easily understandable
Now, enter SCCM 2010 and SUP.
The first thing i HAD to know was the last thing i learned. And not from Microsoft.That is that there is really only one method now, imposed by limitations on Software Update Groups and Deployment packages. You can only create a package of 1000 or less updates
This means chopping up your historic updates and having them deployed as a separate strategy from your newer updates cycles
Secondly, every month from now on you will need to create and sort your updates into a meaningful Update Group and Deployment package - even if you set up an Automatic Deployment rule, you still need to manually create your Update Groups
You can only have one deployment package per update group and will need one software update group per "type" of install (available or Required) AND you will need one software update group and deployment package PER COLLECTION!
To make this work as simply as possible, it will mean having two collections Available and Required (for example)
Each collection will have a SUG associated with it (each with a limit of 1000 updates remember). Each group of circa 1000 updates takes about 2+ hours to compile and you will have a minimum of 5 groups per collection to get up to October 2014
After this your ADRs should now do it all for you but lack the ability to create update groups so you have to do this manually every month beforehand. Whew!!
Thirdly, in the background, WSUS still downloads metadata. In SCCM you should be pointing every update group manually to this folder. Same with Deployment packages and ADRs. Why is this not built-in - intuitive? These are then copied and downloaded as full
packages into their respectively (manually) created source folders
Now, when updates expire or are superseded, you have to manually replace them from each SUG
And also quite a big thing i havent heard anyone else comment on, is the fact that these updates are now NOT shown in the Windows Update feature - they now appear in the Software Center - so now the Servers i sent "Available" updates have to be
logged onto and manually installed - instead of being able to individually target them like i did with PSEXEC and wuauclt
And logging?? There are at least 100 different logs to look at using the Trace Log Tool. It's a full time job just figuring out what logs to look at to resolve any problems
This is, in my opinion, a really poor effort and the documentaion is wildly inconsistent across many forums.
Some kind of standard document is needed. And i say this after having followed Microsoft's own documentation and using technet forums
I, for one, just need one BIG question answered for now - how do i remove the SCCM SUP client and revert back to wuauclt on all my clients - if i remove SUP from SCCM will it remove the client from the clients?

HI Jason,
I have spent a long time trying to get this to work. My requirements are to have WSUS deploy updates automatically with as little intervention as possible and to be able to explain and show the process to others who will administer the system long after
I've gone
The reason I still have to think of things in the WSUS way is that I have a broken update infrastructure that doesn't do what my requirements are. So I now currently need to log into all my "Available " Servers to update them manually instead of
being able to remotely execute the updates. I'll look at the SDK but this is the first time I've heard of it
From the top - yes I agree that's a typo it's Update Goups that can only have 1000 updates. Do you agree that this causes a problem for this scenario? Updates since before 2013 amount to several thousand and so I have to break these up into groups of 1000
- one each for Available and Required groups. That means 8 groups straight away
Having to cater for these historic updates means painfully waiting 2 hours or so for each package to be created. I've done this already and its not pretty but its essential (unless I'm doing it wrong but I am following TechNet forums)
My ADRs will absolutely not create the Update Groups and the docs I have read also say that this is a manual monthly process - Create a Group every month and then use an ADR to use that group - is that not correct?
Update groups - you are mixing my words up and saying the same thing in a different way - "Update groups can absolutely have multiple deployments targeted to different collections" change the "can" for a "must" and you see my
problem. You cannot create a single Update Group, package it up and the deploy it to both Available and Required groups. You need two update groups for this. One for available and one for Required.
Metadata - OK then what is it that WSUS downloads to E:\WSUS\WsusContent\... ? And why is this to be set as the download location for any Update Group, Deployment Package or ADR?? I have to create or select a deployment package which is another
manually created folder under "sources" for which the download location is set to my WSUS folder. This doesn't work unless I set my download location to Microsoft. But WSUS should already have synced in the background to WsusContent so why would
I want to download from Microsoft. And I only want to actually download the "approved" packages. So as far as I'm aware the WSUS\WsusContent folder only contains metadata which is not downloaded until required. Am I wrong? What/who/how downloads
the binaries and when?
Lastly, What doesn't make sense? The goal used to be automation. If and when I needed to, I used to be able to manually intervene for single or multiple devices using PSEXEC to run wuauclt. With SCCM I can see for example, 2x non compliant devices just now.
In the old days I would just psexec onto them and run wuauclt. In SCCM I err... Hmmm.. what? What do I do? Will look at the SDK
Just one other thing - is there no way at all to continue to use the Windows UPdate control panel and have it show the same available updates as Software Centre? Why can SCCM not just work like Windows Update does? If I run Windows Update on any server it
says up do date but if go to Microsoft to check it always comes back with updates
I just want my internal SCCM SUP to work the same way Microsoft updates works for an internet connected computer. Completely Automatic. No intervention. My group of Availabel servers I would like to be able to remotely and individually install from either
a central console or a script. Again, I will look at the SDK for this
Thanks for your reply and advice. I'll give it one more week. ;-)

MDT 2012 - Litetouch deploy windows 8 with different administrator account

I have created and captured a custom image of Windows 8 using MDT2012 update 1 and Windows ADK (without SCCM). In the image, I have set an account called DeployUser, with password XXX, adding it to the Administrators group, and I have disabled the User
Account Control.
I did this because the Administrator account is renamed from GPO and the password is changed every 30 days (for security reasons, the password is not disclosed to any IT support).
Next, I created a TS to deploy this image, adding the installation of some software.
In the Unattend.xml, I also added DeployUser to perform the autologon.
After the first logon with DeployUser, the TS stops and does not return any error message.
If I manually run C: \ ProgramData \ Microsoft \ Windows \ Start Menu \ Programs \ Start-up \ LiteTouch.lnk nothing happens, however, if I run it with "Run as Administrator", the TS continues normally.
Somebody who knows a solution for this?

I believe MDT LiteTouch deployments only recognize the Administrator account name for processing task sequences.
Are you joining the domain during an MDT Litetouch deployment? If so, you may want to delay joining to a domain or GPO processing. Take a look at these recommendations:
Domain Policies that break MDT 2010
It may also be possible to disable GPO processing until the end of the taks sequence via a reghack or disabling a service. Take a look at this:
How to Disable/Enable Group Policy
BTW, the task sequence engine in ConfigMgr prevents GPO processing during an OSD.
V/R, Darrick West - Senior Systems Engineer, ConfigMgr: OSD

Can we re-activate Adobe patches once expired in SCUP and syncronized to WSUS and SCCM 2012 as expired?

Hi,
I expired a couple of Adobe patches in SCUP and published them in WSUS. They got synchronized in WSUS and SCCM as expired. After about two weeks those expired patches got cleaned from SCCM ( at least from UI).
I want to activate them again in SCUP and re-publish as active patches in SCCM. But its not working - I've tried WSUS cleanup and SCUP cleanup already!
Is there any way to re-active expired patches published by SCUP in WSUS and SCCM ? & How?
Excerpt from SCUP.Log:
PublishItem: Item 'Reader Multi Lingual User Interface 10.1.4 Update (UpdateId:'5c22235f-a3d9-48db-95eb-a60ec1886e8e' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')' is on the update server and is expired, no publish actions are possible.

The key here is knowing WHY those updates were "expired" in the first place.
Most likely they were expired because they superseded another update. If so, merely duplicating and publishing won't achieve anything, because the duplicated/re-published update will also be superseded and get promptly expired again.
Ergo, if expired because superseded, the superseding package will need to be customized to remove the supersession references and it also will need to be republished, which also means that certain other considerations may need to be taken as well ... such
as the fact that you now have multiple packages that will conflict with one another that no longer have the requisite supersession metadata.
Regarding this scenario. Configuration Manager 2012 introduced the option to NOT EXPIRE superseded updates, or to defer the expiration for a specified number of days. This is not a SCUP thing; it's a ConfigMgr thing.
Configure the ConfigMgr product to behave the way you desire. Problem solved. :)
If YOU actually expired them in SCUP... then just UNEXPIRE them and republish. Shouldn't be any need to duplicate and republish. This is what Microsoft does all the time. Expire Update 'A' Rev 100 on Monday; publish Update 'A' Rev 101 on Patch Tuesday.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Use share located at server without SCCM roles

Hi,
The scenario is the following: sccm 2012 R2.
2 servers: first one is the server where sccm was installed and is DP too. Second server only is DP.
I need to deploy aditional software which source files are located at third server (without sccm roles).
Problem: When creating additional packages, I use a share located at the third server, and distribute the content to the second server (only DP role), but the package never distribute to the DP (in the sccm console I get an
error).
The question is:
It is possible to use source files located at a server without sccm roles?
Thanks in advance!

Source file access by the site server has nothing to do with the network access account.
Yes, the computer account for the site server must have access to the UNC where the source files are located -- both NTFS and share permissions (as Jörgen mentioned) There's no need to make it a local admin.
Note that the location of the source files has nothing to do with where the clients get those files from; clients always get source files from DPs.
Jason | http://blog.configmgrftw.com

Partial integration of WSUS and SCCM SP1

Hi,
We have an environment with a CAS and nine primary sites. The primary sites are geographically located in different countries. Each country currently manages it's own external WSUS environment, downloading their relevant language packs, etc. Group policy
is applied at a country level to direct clients to the WSUS server.
We would like to install the SUP on our local primary site. I am aware that to do so I need to install the SUP (with WSUS) on the CAS before the role is available on my primary site.
Can anyone confirm the impact of this on the other countries? If they do not install the SUP on their local primary site servers, then I would assume that the external, standalone WSUS infrastructure will continue to operate without issue independent of
SCCM?
My understanding is that there should be no impact, but I need some documentation to support this. If anyone has any links I would appreciate it.

You won't find any documentation because it's not exactly a supported path but it will work and no else will be impacted. This has nothing to do with a possible conflict though as none is really possible because a stand-alone WSUS infrastructure is
completely independent of the WSUS instances stood-up for ConfigMgr and they won't even know about each other.
Ultimately, the clients will use whatever WSUS infrastructure that group policy points them to -- ConfigMgr doesn't do anything to get in the way of this even if they stand up a SUP in their primary site. without a SUP in their primary site though, the clients
won't even enable their software updates client so there's no overlap whatsoever. As long as the GPO is in place though, it will override anything in ConfigMgr as far as WSUS goes.
Note however though that if someone else wants to start using Software Updates in ConfigMgr in the future, you may run into issues because at that point you *must* share the same update catalog (remember that when integrated into ConfigMgr, WSUS is only
responsible for the update catalog and not updates).
As a side comment, I hope you didn't pay whoever recommended 9 primary sites very much because they robbed you (unless of course you actually have like 500,000 managed clients).
Jason | http://blog.configmgrftw.com

WSUS and SCCM configuration

I recently started a new position and have been asked to re setup their updates through sccm. Now im not that experienced since my last position had a fubar WSUS server but this one seems to be simple and kind of working.
The configuration is as follows.
SCCM SUP points to MSUpdate
Clients look at MSUpdate and never sees SUP
WSUS looks at MSUpate and hasn't downstream sync'd to sccm in 470+ days.
Now am i wrong for thinking that the flow should looks like Cloud->WSUS->SCCM->Client or should it be Cloud->SCCM->Client with WSUS parallel to SCCM?

Keep in mind that ConfigMgr doesn't use WSUS in the same way as a standalone WSUS implementation. ConfigMgr is basically using the WSUS catalog to find which updates are available. The updates can then be added to Software Update Groups and can then be downloaded
to deployment packages, which in turn can be distributed to DPs and deployed to clients.
Your generalized flow would be Internet ("Cloud")-> ConfigMgr server(s) (with all that entails) -> Clients.
Check wsyncmgr.log (site server) for information about why a sync hasn't happened recently. You can also check WUAHandler.log on the clients to see what they're up to.
-Nick O.

Can not deploy Adobe CC with deployment Manager

Hi,
we are trying to deploy Adobe CC with SCCM 2012 R2. While the installation we are getting errors in the PDApp.log:
01/07/15 14:59:30:028 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 4196 | Build Version - 1.7.0.43
01/07/15 14:59:30:029 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 4196 | Logging Level verbosity Set to 4
01/07/15 14:59:30:029 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 4196 | Executing immediate custom action for install mode.
01/07/15 14:59:30:029 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 4196 | The CustomActionData string is : mode=install;sourceDir=C:\WINDOWS\ccmcache\1d\;installDir=;origDB=C:\WINDOWS\ccmcache\1d\ Adobe Creative Cloud Illustrator 2014.msi
01/07/15 14:59:30:029 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 4196 | Successfully executed the immediate custom action for install mode .
01/07/15 14:59:32:461 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Build Version - 1.7.0.43
01/07/15 14:59:32:461 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Logging Level verbosity Set to 4
01/07/15 14:59:32:461 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Executing the deferred custom action.
01/07/15 14:59:32:466 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Obtained the following as CustomActionData
01/07/15 14:59:32:466 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | mode=install;sourceDir=C:\WINDOWS\ccmcache\1d\;installDir=;origDB=C:\WINDOWS\ccmcache\1d\ Adobe Creative Cloud Illustrator 2014.msi
01/07/15 14:59:32:466 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | mode=install;sourceDir=C:\WINDOWS\ccmcache\1d\;installDir=;origDB=C:\WINDOWS\ccmcache\1d\ Adobe Creative Cloud Illustrator 2014.msi
01/07/15 14:59:32:466 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Original database path is : C:\WINDOWS\ccmcache\1d\Adobe Creative Cloud Illustrator 2014.msi
01/07/15 14:59:32:472 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | OptionXML saved at location :: C:\WINDOWS\TEMP\{C1921A81-A734-45BA-BE0B-E4440C3E2259}\\{CF57953C-5FB8-414D-AF1D-C555914C 4B73}
01/07/15 14:59:32:496 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Build Version - 1.7.0.43
01/07/15 14:59:32:496 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Logging Level verbosity Set to 4
01/07/15 14:59:32:496 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Initializing Custom Action Data from parameters
01/07/15 14:59:32:496 | [INFO] | | ASU | DeploymentManager | Utilities | | | 3796 | Folder does not exist
01/07/15 14:59:32:496 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Provisioning Tool path is (C:\WINDOWS\TEMP\{C1921A81-A734-45BA-BE0B-E4440C3E2259}\\{FF74F6C4-0D5C-43E0-98F2-5A9B0B3 FED97}).
01/07/15 14:59:32:498 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Starting to run the custom action for install mode
01/07/15 14:59:32:498 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | STEP 1: Starting to parse Option XML.
01/07/15 14:59:32:503 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Self-Update BootStrapper Relative Path doesn't exist.
01/07/15 14:59:32:504 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | No of updates found (1).
01/07/15 14:59:32:504 | [WARN] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Failed to find Royalty Bearing attribute info.
01/07/15 14:59:32:504 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Number of Medias found = 1
01/07/15 14:59:32:504 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Deployment Manager is running in Install Mode.
01/07/15 14:59:32:508 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Deployment XML created at path :: C:\WINDOWS\TEMP\{2C2F5292-0608-47D5-BCE2-3B2D1A59C1EC}\\{DE6BF6FD-0D94-4F7D-86B5-6804037C B0D7}
01/07/15 14:59:32:513 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Override XML created at path :: C:\WINDOWS\TEMP\{2C2F5292-0608-47D5-BCE2-3B2D1A59C1EC}\\{0B4F1D68-9714-494B-BF52-CCB490BD 2AF4}
01/07/15 14:59:32:517 | [WARN] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Failed to find the pdb database.
01/07/15 14:59:32:517 | [WARN] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Failed to get the local payload database handle.
01/07/15 14:59:32:517 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | STEP 2: Starting to launch ASU AAM.
01/07/15 14:59:32:517 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Bootstrapper launch location is :: C:\WINDOWS\ccmcache\1d\ASU\Set-up.dat
01/07/15 14:59:32:681 | [INFO] | | ASU | OPM | OPM | | | 4388 | Build Version - 8.0.1.12
01/07/15 14:59:32:681 | [INFO] | | ASU | OPM | OPM | | | 4388 | Logging Level verbosity Set to 4
01/07/15 14:59:32:711 | [WARN] | | ASU | OPM | OPM | | | 4388 | Failed in key1 generation
01/07/15 14:59:32:711 | [WARN] | | ASU | OPM | CryptEngine | | | 4388 | Failed in key1 generation
01/07/15 14:59:32:747 | [WARN] | | ASU | OPM | OPM | | | 4388 | Failed in key3List generation
01/07/15 14:59:32:747 | [ERROR] | | ASU | OPM | CryptEngine | | | 4388 | Failed in key3List generation
01/07/15 14:59:32:749 | [INFO] | | ASU | OPM | OPM | | | 4388 | Schema version and schema compatibility version are same or greater than current
01/07/15 14:59:32:773 | [INFO] | | ASU | OPM | OPM | | | 4388 | _opm_handle_OPDReturnedStatus called with opdStatus as:0
01/07/15 14:59:32:773 | [INFO] | | ASU | OPM | OPM | | | 4388 | No Record found for the input fields in opm_getValueForKey
01/07/15 14:59:32:774 | [INFO] | | ASU | OPM | OPM | | | 4388 | Released OPM refrence successfully in opm_freeLibRef
01/07/15 14:59:32:840 | [INFO] | | ASU | PIM | PIM | | | 4160 | Build Version - 2.8.1.451
01/07/15 14:59:32:840 | [INFO] | | ASU | PIM | PIM | | | 4160 | Logging Level verbosity Set to 4
01/07/15 14:59:32:849 | [INFO] | | ASU | PIM | PIM | | | 4160 | Build Version - 2.8.1.451
01/07/15 14:59:32:850 | [INFO] | | ASU | PIM | PIM | | | 4160 | Logging Level verbosity Set to 4
01/07/15 14:59:32:850 | [WARN] | | ASU | PIM | PIM | | | 4160 | Detected db journal file trying to repair it...
01/07/15 14:59:32:850 | [INFO] | | ASU | PIM | PIM | | | 4160 | trying to createOrUpdatePIMDbSchema.
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | Current db schema version on machine 2.
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | Current db schema version to install 2.
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | PIM DB Schema is up to date. Current schema version is 2.
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | PIM Database is Up To Date.
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | Sqlite 'Successfully' recovered from journal file.
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | PIMSqlite closeDB status 0
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | Build Version - 2.8.1.451
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | Logging Level verbosity Set to 4
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | Creating PIM instance for path: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp
01/07/15 14:59:32:852 | [FATAL] | | ASU | PIM | PIM | | | 4160 | Detected db journal file, Application is in corrupted state: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp
01/07/15 14:59:32:852 | [INFO] | | ASU | PIM | PIM | | | 4160 | sqlite(pim.db) at path C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp is already closed
01/07/15 14:59:32:852 | [ERROR] | | ASU | PIM | PIM | | | 4160 | Failed to create the pimLibraryRef
01/07/15 14:59:32:852 | [ERROR] | | ASU | PIM | PIM | | | 4160 | Successfully freed PIM object Array
01/07/15 14:59:32:869 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Build Version - 1.7.0.43
01/07/15 14:59:32:869 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Logging Level verbosity Set to 4
01/07/15 14:59:32:869 | [FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | The Bootstrapper Process is (62).Stopping the installation process.
01/07/15 14:59:32:869 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Starting to clean the partially installed payloads.
01/07/15 14:59:32:874 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Undeployment XML created at path :: C:\WINDOWS\TEMP\{2C2F5292-0608-47D5-BCE2-3B2D1A59C1EC}\\{FEBD9916-0002-4AFE-9DE5-08A59CA0 479A}
01/07/15 14:59:32:874 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Starting to launch the Adobe Installer for uninstall mode.
01/07/15 14:59:32:874 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Obtained Adobe Common Folder Path.
01/07/15 14:59:32:874 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\DECore\Setup.exe
01/07/15 14:59:32:993 | [INFO] | | ASU | DeploymentManager | AAMEEUtilities | | | 3796 | Process creation completed.
01/07/15 14:59:32:994 | [FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | The return code from the Adobe Installer Process is (33).Stopping the uninstallation process.
01/07/15 14:59:32:994 | [WARN] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Failed to find the pdb database.
01/07/15 14:59:32:994 | [WARN] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | Failed to get the local payload database handle.
01/07/15 14:59:32:994 | [INFO] | | ASU | DeploymentManager | Utilities | | | 3796 | Folder does not exist
01/07/15 14:59:33:001 | [INFO] | | ASU | OPM | OPM | | | 3796 | Build Version - 8.0.0.143
01/07/15 14:59:33:001 | [INFO] | | ASU | OPM | OPM | | | 3796 | Logging Level verbosity Set to 4
01/07/15 14:59:33:015 | [WARN] | | ASU | OPM | OPM | | | 3796 | Failed in key1 generation
01/07/15 14:59:33:015 | [WARN] | | ASU | OPM | CryptEngine | | | 3796 | Failed in key1 generation
01/07/15 14:59:33:046 | [WARN] | | ASU | OPM | OPM | | | 3796 | Failed in key3List generation
01/07/15 14:59:33:046 | [ERROR] | | ASU | OPM | CryptEngine | | | 3796 | Failed in key3List generation
01/07/15 14:59:33:048 | [INFO] | | ASU | OPM | OPM | | | 3796 | Schema version and schema compatibility version are same or greater than current
01/07/15 14:59:33:077 | [INFO] | | ASU | OPM | OPM | | | 3796 | _opm_handle_OPDReturnedStatus called with opdStatus as:0
01/07/15 14:59:33:078 | [INFO] | | ASU | OPM | OPM | | | 3796 | No Record found for the input fields in opm_getValueForKey
01/07/15 14:59:33:078 | [INFO] | | ASU | OPM | OPM | | | 3796 | Released OPM refrence successfully in opm_freeLibRef
01/07/15 14:59:33:100 | [INFO] | | ASU | DeploymentManager | | | | 3796 | Event Guid generated is: 'af2ccd85-1900-4b4e-b396-c2d165eb28df'
01/07/15 14:59:33:103 | [INFO] | | ASU | DeploymentManager | | | | 3796 | GetIEProxyInfo - No default proxy present on the user machine
01/07/15 14:59:33:104 | [INFO] | | ASU | DeploymentManager | | | | 3796 | GetIEProxyInfo - Failed to get proxy for the url, error:12006
01/07/15 14:59:33:104 | [INFO] | | ASU | DeploymentManager | | | | 3796 | GetIEProxyInfo - proxy Url is
01/07/15 14:59:33:561 | [INFO] | | ASU | DeploymentManager | | | | 3240 | HTTP Request Status code 200.
01/07/15 14:59:33:574 | [INFO] | | ASU | DeploymentManager | | | | 3796 | The http request returned HTTP_Status:0 HttpCommunicator error:0
01/07/15 14:59:33:574 | [INFO] | | ASU | DeploymentManager | | | | 3796 | Waiting for the async thread to get the task completed
01/07/15 14:59:33:581 | [INFO] | | ASU | DeploymentManager | | | | 4664 | Async thread is completed. Now exiting from function.
01/07/15 14:59:33:625 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 3796 | The install workflow is terminating.
Can anybody please help us?
Thank you.
Stefan

Stefan,
Possibly dumb question but are your installers built for the appropriate architecture (32-, 64-bit)? Adobe is pretty picky about that with CC.

Deploy FEP definitions with WSUS without SCCM.

Similar Messages

Maybe you are looking for