Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Posts posted by tike100

  1. Yes the boundaries look correct from what you have done.


    Have you distributed the packages out?

    Looking through your SMS log you have not set a Network Access Account, which is used to download the packages. Forgive me for not knowing how to set that off the top of my head, but you should be able to find that easily amongst the settings under your main site. If not Google should be able to help :)

  2. Hi All,


    Hope someone can help :) I've got a Hyper V server running two VM's. One with snapshots is causing me problems... its taking up 27gb worth of space!


    Its causing the hosts disk space to run low and therefore putting the VM into the "Paused-Critical" state.


    When I try to delete the VM snapshots, I'm getting the below error =


    "Cannot delete snapshot: the system cannot find the file specified. (0x80070002).


    *Servername* failed to remove snapshot. (Virtual machine ID 4FC19371-AE2C-4D4D-8AF8-D985EC6553F0)


    Cannot delete snapshot: the system cannot find the file specified. (0x80070002). (Snapshot ID 5D32D54D-336A-4598-A5B4-41BC824F1537)."



    Hard drive location = 1 VHD on "F:\"

    Snapshot file location = "C:\program data\microsoft\windows\hyper-v"


    I've tried exporting the VM to then re-import it with no luck....


    "*Servername* failed to export. (Virtual machine ID 4FC19371-AE2C-4D4D-8AF8-D985EC6553F0)"






  3. Yes - get boundaries set up and that should eliminate that aspect.


    Manually creating packages on a seperate site is also a big no no, SCCM relies heavily on self generated certificates that it creates when distributing from primary site (I forget the file name) but it does logical checking on a DP each day to confirm its in place and correct.


    Also in the advertisement, tick the option to allow the package to failover to another DP if the package cannot be found on the local DP......


    Depending on your bandwidth between sites that should help to resolve the issue quickly :)

  4. Where's your source location for these drivers? SCCM gets very funny about referencing drivers via a UNC path.


    Best practice is to have the drivers required held on the SCCM server and reference them via a drive path E.G "D:\drivers\....."


    Have you enabled the F8 function of your TS, with this enabled you can open a cmd prompt from inside the TS.


    Normally in SCCM when the TS fails you get 15minutes grace when it counts down to restart? During this time press F8 and navigate to "C:\program files\ccm\logs" and take off the log files, this will show you what is causing the problem.


    Hope that helps



  5. Actually I have done both. In this case I am launching the TSM disk on a Hyper-V VM "shell" (no OS, just settings and pre-config (sized) hard drive). In the past I have gotten the same result while trying to pull an OS image. In that situation the image being pulled DOES get to the SCCM server up to about 70%-90% then the network drops. I can get it back with a few attempts a ipconfig/renew but at that point the TS has failed.


    To answer your question I suppose I should say PXE as I am starting the process from a TSM disk.


    I do want to be clear that the target machine DOES find and start the TS, but at some point the network drops for seemingly no reason. The same TS works fine on a real machine. I have not tried this on a different VM software (Virtual box/VMware) so I dont know positivly if its Hyper-V or the network but as it works fine on a real machine I lean toward some Hyper-V setting not being right.


    It could be that the drivers are not being injected?


    So whilst its in PXE its running fine, once it drops out of PXE and reboots to continue the TS it cant connect to the SCCM server (NIC drivers missing) and therefore the TS fails??



    That would be my guess........


    Is SCCM reporting anything back?

  6. You'll need to create two queries, the first query is to see if the software is installed, the second is a sub-select query of the first query.


    Once the second query exists you can import this into a collection and advertise to that collection to install.


    The queries are a bit complicated and off the top of my head I cant remember the exact wording but a good link is here =




    Hope that helps :)

  7. I'm having some problems with downstream servers syncing with the upstream server.


    All WSUS Servers are WSUS Server Version: 3.2.7600.256 and I have installed KB2720211 and KB2734608.


    The Database is held in the Windows Internal Database


    The Upstream server is synchronising with Windows Update absolutely fine, and downloading updates OK.


    The three downstream servers however are not. They are reporting as failed with the below message =


    Result = An error occurred with the server’s data store.


    Clicking Details shows the below detailed message =


    SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
    at System.Data.SqlClient.SqlDataReader.Read()
    at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ReadOneRow()
    at Microsoft.UpdateServices.Internal.DataAccess.HideUpdatesForReplicaSync(String xmlUpdateIds)
    at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ProcessHiddenUpdates(Guid[] hiddenUpdates)
    at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ReplicaSync()
    at Microsoft.UpdateServic


    Whats also weird is the computer status is being sync’d to the upstream server and the downstream servers are downloading new updates, yet the sync is still failing?

    Can anyone shed some light?


    The upstream server = Server 2003

    1 Downstream server = Server 2008 R2

    2 Downstream Servers = Server 2003

  8. All,


    I am trying to deploy windows Xp via SCCM. I have SCCM set up correctly - It was working!


    Yesterday I added in 1 driver... It failed deploying so I thought "OK" and removed it from the package and updated the distribution point...... NOW - I cant build the machine that worked absolutely fine yesterday!!


    I have been through the SMSTS.log and the ZTIValidate.log which i've taken off the root of the machine thats failing.


    The machine fails just after applying driver packages - I have it set up so that it applies the HDD driver first - and then everything else!


    This is whilst being in PXE so network and HDD drivers allow this stage fine.


    I am unable to provide any screen shots or log reports as thats potentially damaging to my organisation - appologies.


    Any thoughts?



    Please help!

  • Create New...