App-V 5.0 Streaming over SCCM 2012 SP1 - High Availability / Load Balancig

Hello Anybody,
the default App-V 5.0 Streaming (SharedContentStoreMode = on) Deployment over SCCM belongs to a HTTP-Streaming over http:\\SCCM-Server\... . The whole content flows from SCCM to the App-V-Client. Is it possible to create there a high availability solution?
Yes, we can set a second distribution point. But in th App-V-Client are always only one Distribution Source.
Is it possible to set there an clustered adress of an other IIS? Is it possible to change the publishing Distribution Source with an SMB-Path to File-Cluster? Is there a trick with Source-Root-Parameter in App-V-Client? Or are ther anything else to create
a high availibility App-V-Streaming-Solution?
Yes, with App-V-Management-Server there is a high availability solution. - But we have only SCCM-Infrastruktur for App-V-Distribution.
Thank you, best regards
Daniel

Daniel, do you found solution?

Similar Messages

  • App-V 5 Virtual Environments in SCCM 2012 SP1

    I am attempting to use SCCM 2012 SP1 to Deploy App-V v5 Applications.  So far deploying applications to user groups (like I did with 4.6) seem to work well.  The only issue that I am having is deploying Virtual Environments (the new way of
    "dynamic sequencing).  My problem is that on the client side, the App Connection Groups are not being populated.  What can I do to fix this?  The applications are deployed to a user group collection and not a machine collection.  From
    what I have found this is possible but it is not working for me.  Anything to help is GREATLY appreciated!!
    Brian

    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

  • App-V 5.0SP2 question with SCCM 2012 CU4 (functionality vs full support with R2)

    I understand that for App-V 5.0 SP2 and SCCM 2012 SP1 integration at least CU4 is required but R2 with CU1 for full functionality.
    I’ve attached an image from some session that someone else gave me. I have questions after looking at the slide since there are no details on what is not fully supported with CU4 pre R2.
    Since we have immediate plans to add CU4 to our SCCM 2012 SP1 environment can anyone please give us a break down of what functionality is not available in App-V 5.0 SP2 before we go all the way up to SCCM 2012 R2?
    On another note does anyone have any clue what TechED session that was from so I can see the replay?
    Thanks very much for any info on this.

    Hello,
    As per the slide - CU1 is required for full support with R2.
    See this article;
    http://support.microsoft.com/kb/2938441
    Application Virtualization
    This cumulative update adds support for Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2). The following issues are seen only in App-V 5.0 SP2 environments earlier than CU1:
    With App-V 5.0 SP2, when a new version of an App-V package supersedes an earlier version, and when that earlier version is being used, the package is listed as not published. Errors that resemble the following are logged in the AppEnforce.log and the AppDiscovery.log
    files.
    AppEnforce.log
    Publish-AppvClientPackage : A publish operation has been scheduled, pending
    the shutdown of all applications in the package or the connection group.
    Publishing Package is successful but one one of the Virtual Package is currently in use. Close this Virtual Package to get the changes into effect
    Performing detection of app deployment type TestApp - Microsoft Application Virtualization 5(ScopeId_0C7279F0-1490-4A0E-A7A3-32A000CEF76D/DeploymentType_d1adf427-ac14-4ee1-9e51-415af7675383, revision 2) for system.
    AppDiscovery.log
    Required component [{AppVPackageRoot}]\TestApp.exe is not published
    With App-V 5.0 SP2, App-V packages that are being used cannot be uninstalled. Errors that resemble the following are logged in the AppEnforce.log file:
    CVEWorker::UninstallConnectionGroup() failed
    Nicke Källén | The Knack| Twitter:
    @Znackattack

  • App v package distribution issue to sccm 2012 DP

    Hi,
    We are migrating app-v 4.6 packages to sccm 2012 , after importing the packages when we update DP its not copying the dependent scripts inside the appv package to Dp and hence when application launches it fails to launch the vb script.
    the script is made to run when shortcut is launched, but no vb script is copied to DP , but I have all files intact in source folder iyt just copies .sprj,xml,osd.
    Please suggest how to make all the files in package abcd.001 to get copied in DP.
    Does App-v package distribution is different from normal package.
    Thanks
    Shuaib

    Open up the app in the sequencer, add the file to your scripts folder. If the script requires to be run elevated, you'll want to use the Deployment config file and use Global publishing....
    If you don't need elevation you can use the User Config and won't need to publish globally.
    Fore more info and some examples, check this out:
    http://blogs.technet.com/b/appv/archive/2012/12/10/scripting-and-embedded-scripting-for-appv-5-0-dynamic-deployment-and-user-configuration-scripting.aspx
    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
    rorymon.com Twitter: @Rorymon

  • Declaring an SCCM 2012 SP1 server as the "Publishing Server" for App-V 5 SP2

    Good morning everyone.
    I'm trying to virtualize Adobe Flash 10.3 for IE.  That's beside the point but I wanted to mention my ultimate goal.
    Sparing you all the App-V stuff I have to go through there's one obstacle that is hindering me at this point.
    I've converted completely to CM 2012 SP1 for my App-V deployment functions but find myself needing to specify our main CM server as the "AppVPublishingServer".  The ultimate goal here is to set the virtual app attribute of "IsPublishedGlobally"
    to TRUE.  I need to refer to the Publishing Server's URL in order to use the PoSH command "Set-AppVpublishingserver" to manipulate the "Global" parameters.
    Do any of you know how to configure this attrib through CM, or, how to declare the CM server as a Publishing Server (in App-V's eyes)?
    Thanks very much.
    IAmStrings

    Hello,
    If using SCCM and the App-V 5 integration, you can never configure a publishing server.
    Read this whitepaper for the full-story;
    http://blogs.technet.com/b/virtualvibes/archive/2013/04/22/sccm-2012-sp1-and-app-v-5-0-documentation.aspx
    It contains step-by-step instructions on howto use the integration.
    Nicke Källén | The Knack| Twitter:
    @Znackattack

  • SCCM 2012 SP1 - Offline Servicing failure - Failed to find or access the update binaries to be applied on the image

    Hi there
    Trying to patch a new Windows 7 SP1 image within SCCM 2012 SP1, but it's failing.
    I've searched for information on the failure messages I am seeing, but although there is a LOT of information online concerning Offline Servicing failures, I can't find anything on the errors I am seeing.
    I've tried injecting a single update, five updates and ten updates, no difference, same messages.
    We have McAfee Access Protection disabled, as we know Offline Servicing simply won't work if this is running.
    In the console, in Schedule Update Status for the image I am trying to update, the following message is shown:
    "Failed to find or access the update binaries to be applied on the image."
    That sounds as if the process can't find the actual .cab file for any update I've tried to inject, but I don't know why it wouldn't be able to do that, we have Software Updates configured and the .cab files are on the same server.
    When I looked at the OfflineServicingMgr.log file, I see the following entries:
    Processing image at index 1        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:52:49        8272 (0x2050)
    Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\PackageID\W7_Image.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\PackageID\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'        SMS_OFFLINE_SERVICING_MANAGER       
    14/06/2014 14:52:49        8272 (0x2050)
    Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17514        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31       
    8272 (0x2050)
    Failed to find properties of file 4        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
    UnMounting Image (Commit Changes = 0) ...        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
    Completed processing image package PackageID. Status = Failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    Updated history for image package PackageID in the database        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    Schedule processing failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    Processing completed for Schedule with ID 16777237        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMServer.domain SITE=Site_Code PID=8560 TID=8272 GMTDATE=Sat Jun 14 13:54:04.964 2014 ISTR0="16777237" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0        SMS_OFFLINE_SERVICING_MANAGER       
    14/06/2014 14:54:04        8272 (0x2050)
    Schedule processing thread stopped        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:05        8272 (0x2050)
    I'm not sure what file "Failed to find properties of file 4" is referring to, whether dism.exe, an update or the image itself, but immediately after this message appears the image is unmounted. After that this message shows:
    "Completed processing image package PackageID. Status = Failed"
    As I say, there's a lot of information available re Offline Servicing but I haven't found anything with these particular messages.
    If anyone has encountered this before, I'd appreciate any information you have.
    Regards,
    John.

    Hi,
    I think file named 'NO_SMS_ON_DRIVE.SMS’ might be causing this issue. If this file is present in logical drives, then please give it a shot one more time after deleting this file from the logical drives.
    Due to this file, it might be preventing 'smsexec' service to skip the drive when looking for content. So worth a try!
    After deleting this file, you also need to restart 'smsexec' service to reflect the changes. You can also verify from below registry value & ensure that all of your logical drives (specially where SCCMContentLib directory resides) should be listed
    over there 
    'HKLM\Software\Microsoft\SMS\DP\ContentLibUsableDrives'
    Hope this will help!
    Cheers | Navdeep Sidhu

  • Office 2013 Professional Plus - 32 bit Deployment takes an unacceptable time to deploy in SCCM 2012 - SP1 CU3

    We recently migrated over to SCCM 2012 SP1 - CU3 the first of the year from SCCM 2007 SP2.  We have used SCCM in the past to deploy Office 2010 and had deployed Office 2013 to our IT Dept. before moving over to SCCM 2012.  The deployment went as
    expected.  Now that we are ready to start deploying Office 2013 to our corporate workstations, the deployment time is running 4.5 hours to 5.5 hours from the local site server DP.  I am afraid to find out what time we are looking at for remote DP's. 
    The three factors that are different is that our SCCM site server is virtual, it is running 2012 for the OS, and obviously SCCM 2012-SP1 - CU3.   We are using the same package source files.   Previous to a successful deployment we were
    seeing hash mismatch errors which MS support pointed us to the nic driver on the VM was using E1000E and to change it to a VMX something driver.
    So I guess my question is anyone else out there deploying Office 2013 ProPlus - 32 bit from this type of environment?  Our previous deployment time for office was a little over an hour (not five hours).  Any suggestions where to look to improve
    the deployment time? 
    I am expected to deploy this in one week and have been working on these issues for weeks.

    I see now that you are using a combination of scripts and ConfigMgr package/program.
    The AppEnforce.log file is for use with the new ConfigMgr Application model.
    Is there any reason that you don't use the new model for deploying Office 2013? It's a single step process and perfect for it. If you use the Office Customisation Tool you can customise what you like. The process will then uninstall Office 2010 and install
    Office 2013.
    This is how you do it
    http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_9368.html
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Reporting services keep failing on SCCM 2012 SP1

    I have SCCM 2012 SP1 install with SSRS 2012 install on same server 2008 R2 server.
    Reporting services keep failing with the following message when trying to START the service from the Reporting Services Configuration Manager Console
    System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
       at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
       at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
    Thx,
    Joe
    Thx, Joe

    Good advice Garth, but I have opened over 5 cases to try to resolve this and several other issues with my troublesome SCOM 2012 SP1 upgrade. That is why I am also sending it to the community in hope they can provide assistance.
    CSS will only work on one specific issue and in most cases these are targeted bandaid fixes that DO NOT address the underlying or related issues. I a left to opening many tickets and still floundering with a unreliable product.
    It seems to only be with System Center. All other products by Microsoft seem to be reliable and predicable and are easily supported using break fix support model of the current MS teams.
    It is SQL (SSRS) that controls subscriptions not CM12. CM12 only leverages the APIs provided by SQL (SSRS).
    I hate to say this but Why do you think this problem has anything to do with CM12?
    If CSS tell you to re-create the subscription and the problem re-occurs then I would re-open the ticket and tell them that the problem is NOT fixed and to continue working on it.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

    Hi,
    I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400.  But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
    and not 5.00.7804.1400. 
    For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client? 
    Thanks,
    Nick

    Hi,
    Here's some good information to look over:
    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
    I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
    http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
    Don't retire TechNet! -
    (Don't give up yet - 12,575+ strong and growing)

  • Lync 2013 x64 silent client deployment via SCCM 2012 SP1

    Greetings everyone!
    I ran into a problem with Lync 2013 x64 silent deployment.
    I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
    I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
    Added them as applications to sccm software library.
    Deployment of Lync 2013 x86 application was a success with over than 80% compliance. 
    But all Lync 2013 x64 automatic installations finish with different errors.
    I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
    My membership query-rules for this collection:
    Office 2013 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
    Office 2010 x64
    select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
    = SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
    My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
    So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
    The same configuration works with Lync 2013 x86 deployment, except other setup folders.
    When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
    I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
    Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
    sites with deployment point.
    Thanks in advance.

    Hi,
    Here are some tips and tricks for your reference.
    Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
    http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    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.

  • SQL Connection Failed for SCCM 2012 R2 (Unable to load user-specified certificate)

    We've recently completed an upgrade from SCCM 2012 SP1 to 2012 R2 and have been running in the new environment for about a week. As of this morning, The consoles failed to connect to the CAS' and one of the Primary Site's database. The issue was resolved
    easily enough by addressing a certificate issue in SQL, but I'm left wondering if there's a correlation between the SP1-to-R2 upgrade that would cause the cert to fail. Anyone have experience with this?
    2014-01-21 22:10:11.81 Server      The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
    2014-01-21 22:10:11.81 Server      Error: 26014, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      Unable to load user-specified certificate [Cert Hash(sha1) "haaaaassssshhhh"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See
    "Configuring Certificate for Use by SSL" in Books Online.
    2014-01-21 22:10:11.81 Server      Error: 17182, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-01-21 22:10:11.81 Server      Error: 17182, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-01-21 22:10:11.81 Server      Error: 17826, Severity: 18, State: 3.
    2014-01-21 22:10:11.81 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-01-21 22:10:11.81 Server      Error: 17120, Severity: 16, State: 1.
    2014-01-21 22:10:11.81 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    We got the same certificate related error events after a fresh install of SCCM 2012 R2 on a new server. It happened during the first reboot after SCCM was installed. In the Certificates mmc, I right-clicked on the certificate used by SQL and chose Manage
    Private Keys. Giving the service account that runs the MSSQLSERVER service read rights to the private key allowed SQL to start. However, after a day or so we rebooted the server again, and SQL wouldn't start. Something had removed the service account's read
    permission. Since the SCCM configuration wasn't that far along, we uninstalled SCCM. After giving the service account read rights again, and rebooting several times over a few days, and SQL started every time. We then installed SCCM 2012 R2 again, and checked
    the certificate's permissions before rebooting. The service account still had read permissions when the install completed, but as soon as the server was rebooted, it lost the permissions again.
    The Certificates mmc was then used to request a second computer certificate and then SQL was configured to use that new certificate via SQL Server Configuration Manager. After several days and a number of reboots the SQL services have started normally every
    time so the second certificate seems to have fixed the issue. I have kept the original certificate for fear that removing it will cause whatever part of SCCM 2012 R2 that modifies the original certificate to start removing permissions from the new certificate
    as well.

  • Deploy Windows 8 To Go through SCCM 2012 SP1

    First a little backgroud:
    I have SCCM 2012 SP1 with MDT 2012 Update 1 integrated. I am using an MDT UDI task sequence to deploy windows 8 and it works perfectly. My Windows 8 image is fairly thin (only containing OS updates and C++ runtimes), and I am using the MDT database
    and an MDT task sequence in SCCM 2012  to dynamically set a list of SCCM Applications to install as well as settings based on location. 
    Now I want to get Windows To Go provisioning working in SCCM 2012 SP1. I had a powershell script that preparied the drive and applied a thick image (including office and other apps) to it then updated unattend.xml with a computer name and the domain join
    info.  That worked for me however I'd like to levarage the dynamic task sequence that I described above to build these To Go sticks the same as my other Windows 8 machines without having to keep updating the thick image evertime something changes. 
    There isn't much info out there that Iv'e found on setting up SCCM 2012 SP1 to provision windows to go here are the two that I have found 
    http://ixrv.blogspot.com/2012/10/provisioning-windows-8-to-go-with.html
    http://technet.microsoft.com/en-us/library/jj651035.aspx
    I followed the instructions in the first link and was able to run the Windows to Go Creator program and apply the prestaged wim to the USB stick. I rebooted from the USB stick Windows PE started and started to run my task sequence then it errored out on
    the apply image step. At this point it occured to me that the MDT SCCM task sequence was probably not setup for prestaged media and or Windows To Go. 
    So my question is am I on the right track? Do I just need to examine each step in my task sequence and make sure that it will work properly with my Prestaged/Windows To Go stick? If so has anyone actually gotten this to work that could give me some advice?
    Or is it asking too much to have a dynamic Windows To Go task sequence and I should just be building a thick image and using a second task sequence specifically for Windows to go? 
    are there any other resources for Windows To Go with SCCM that I'm missing? 
    Thanks, 
    Tony

    First of all sorry I missed your last three posts I have to check my email notifications. I'll try to answer all of them even though I think the last part is the only one where you are still stuck. 
    When I created my prestaged media I didn't put anything into it except for the the OS image and my PE image. On the Select Application and Select Package screen in the prestaged media wizard remove any application or packages that are added automatically.
    The task sequence is supposed to be smart enough to know if the version of the package that is on the prestaged media is out of date and go to a DP to get it but that didnt work for me. The only way I was able to get it to work was to remove all the packages
    from the prestaged media even the Customsettings package, the MDT toolkit package, USMT, etc.. 
    http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d729d0ff-829f-4af8-91af-2131b3355fd0/
    This thread which is about prestaged media in SCCM 2007 helped me to understand how prestaged media is supposed to work. Basically what I learned is that once the computer is rebooted from the ToGo stick into PE the task sequence will run the same as any
    other task sequence installing any applications and setting up your ToGo stick just like any other computer that runs the task sequence they dont need to be in your prestaged media for this to happen. 
    You shouldn't need to worry about partitioning WTGCreator.exe will partition the ToGo stick for you I'm just using the standard MDT Integrated partitioning in my task sequence. The one thing that I did was set the Windows To Go Creator package to "run from
    distribution point" which speed things up because then it didnt download the prestaged wim then apply it to the USB drive. 
    Is it booting into PE then rebooting? Did you check the "Allow unattend operating system deployment" check box when you made your prestaged media? If so it wants you to have set the task sequence to run in a task sequence variable SMSTSPreferredAdvertID
    to the task sequence ID you want to run. I'd just remake the media and leave that box unchecked. 
    Good luck and let me know how it works for you. I'll check back sooner this time I promise. 

  • SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

    Hi All, 
    Good day to all you. 
    I would like to seek all your help on this issue that i have encountering. 
    My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
    Error: 
    Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
    Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
    SMS_WSUS_SYNC_MANAGER  7/22/2014 3:05:32 PM 5776 (0x1690)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
    ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_SYNC_MANAGER  7/22/2014 3:05:32 PM 5776 (0x1690)
    Sync failed. Will retry in 60 minutes
    SMS_WSUS_SYNC_MANAGER  5776 (0x1690)
    below are wsyncmgr.log:
    Setting sync alert to active state on site C01  SMS_WSUS_SYNC_MANAGER (0x1690)
    Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
    5776 (0x1690)
    Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
    5776 (0x1690)
    Starting Sync SMS_WSUS_SYNC_MANAGER
    5776 (0x1690)
    Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
    5776 (0x1690)
    Read SUPs from SCF for MYHQKUL990707S.sdb.com  SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
    Found 1 SUPs SMS_WSUS_SYNC_MANAGER
    5776 (0x1690)
    Found active SUP MYHQKUL990707S.sdb.com from SCF File.
    SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
    5776 (0x1690)
    Synchronizing WSUS server MYHQKUL990707S.sdb.com  SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
    5776 (0x1690)
    Using account sdb\SCCM-Admin to connect to WSUS Server
    SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
    Synchronizing WSUS server myhqkul990707s.sdb.com ...
    SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
    440 (0x01B8)
    Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
    Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
    SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
    5776 (0x1690)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
    ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
    5776 (0x1690)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
    5776 (0x1690)
    All response is much appreciated
    Thank You

    Hi,
    I recommend you look at the IIS log. Maybe it can give us some clues.
    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 2012 SP1 - Build and Capture - ReCapture impossible

    Hi all
    i upgrade my SCCM 2012 RTM to SCCM 2012 SP1 yesterday. Today i started a recapture of my Windows 7 and Windows 2008 R2 Base Image.
    For that i have 2 VMs located in different SCCM Collections. And a Build and Capture Task Sequence is deployed to the collections.
    Before SP1 the behavior was:
    - Reset Required PXE Deployment in SCCM for the VMs
    - Start VM
    - VM boots with PXE
    - VM installs and capture the Installation
    And that i could do all the time so often as i want.
    Now with SP1 it is the same procedure but just for one time. After one success Build and Capture Task, the vm is unable to do the task sequence again. The VM is booting into the PXE and then i can see in the smsts log:
    There are no task sequences available to this computer
    But there are. The Task Sequence is set to "Always rerun".
    The only "fix" is to completely recreate the computer item in sccm.
    What is here wrong? Is this a known bug?
    best
    JBAB

    Hi, your problem is that when you deploy the task over the collation you only specified "media and PXE" was available to and probably the machines that you try to capture already had the sccm client. You can try to deploy the sequence task to a collation
    including the the option "configuration manager, media and PXE", or you can also deploy the task sequence to de "unknown devices" collation and delete the objects of the two virtual machines in configuration manager

  • Cannot install SCCM 2012 SP1 CU4

    Hi,
    I just tried to apply CU4 over one of my SCCM 2012 SP1 CU3 deployments and I receive the following message during the initial verification phase:
    Server update status: This update applies to product version 5.0.7804. The installed version on this computer is 5.0.7958.1000. This update is not applicable to this computer.
    Console update status: No serviceable configuration manager role was found on the local system.
    If I engage the verification phase on this installation for CU2 and CU3 there is no problem at all, so this must be a CU4 package specific error.
    Anybody experiencing the same behavior ?

    The latest CU that I see for SCCM 2012 SP1 is SP1 Cumulative Update 3, are you sure you are working with the proper file?  .
    CU4 was released this week:
    http://blogs.technet.com/b/configurationmgr/archive/2014/01/29/now-available-cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1.aspx
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Maybe you are looking for