Jump to content

Recommended Posts

Posted

Is this a captured WIM or a Task Sequence? (If the latter it could be one of your packages that has the mismatched hash)

Could also be a driver package

 

Guessing the SMSTSLog doesn't help much?

Posted

Its the latter.

 

No the log doesn't help at all.

 

I have removed all packages from my DP but it doesn't seem to be removing the packages from the disk on the DP. Why would that be please? My idea is so i can totally redistribute all my packages from a fresh.

 

Thanks

Posted

Sounds like the DP role is screwed :(

You may need to remove the packages from the DP and then uninstalled the DP(and maybe the Management Point too), remove it from disk, reboot, and start again.

Also remove any Dist groups, etc from within SCCM.

Posted

Yeah that may be a good idea - though if the fault is with SCCM - yo may be backing up the problem too :(

Damn I hate software at times :(

Posted

I have a backup from just before i started all this so should be ok to get back somewhere.

 

If the problem happens on the new server, i might have to shell out for an MS support ticket :(

Posted

Ouch - though at least they will help!

I have 2 free tickets still with my TechNet subs - but holding onto them for dear life! lol

Posted
Right i have opened an MS support case. I have 2 that will expire at the end of the month anyways. Will report back :)
Posted

:( what's their SLA for TechNet/EEE subscribers?

 

Worst Case = Your DB is screwed... and no amount if SCCM rebuilds will help if that is the case :(

 

Really hope that isn't the case though :)

Posted
I have a backup before i start meddling so we should be ok. I haven't go for the server rebuild yet. Just going to see what MS say.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...