turbomcp

yeah thanks, sql is not what it was in sccm 2007 i talked to microsoft about this and i found 3 diffrent bugs in that. they also have no clue why this happens(only on secondary site) we tried it 3-4 times with diffrent setups(more permissions then required diffrent versions of sql) probably will be fixed in newer builds

hi getting this on r2 Sqlexpress install process return -2067919934. even when it managed to install it failed to do the replication anybody had issues like that with secondary site?

Hi first of all wonderfull forum with alot of info second i wanted to get your opinion on something i ran a poc (on vmware workstation) i installed a windows 7 ultimate x86 computer with office 2010(no sccm client) and used the capture cd to capture the image and import it to sccm. i than ran the mdt 2010 client task sequence and wanted to "refresh" an xp machine(with sccm client and lots of docs and settings) to windows 7 at first this failed after booting to winpe because of network issues, i changed the network card to be E1000 and it fixed the problem and continued. eveeyrhing seems to go ok(apply os ...). but after appying the windows 7 image(i verified its applying 2-2 index of the image) the old xp machine boots and i get cannot find ntldr. any idea what can cause this?(i verified the boot sector was applied in the tslog bootsec/nt60..... i am thinking its something with that extra partition(i know there is aknown issue with this thing and capture cd) do i need to have the sccm installed on the refrence 7 machine? anyway would appreciate your help Thanks

i would first dig into hardware(drivers) problem before digging into sccm or sql problems. did you update all drivers to windows 2003(up to date) drivers. tell the customer that most cool features for the server itself and for sccm are in server 2008 and server 2008 R2 better stick to server 2008 64bit version(easy upgrade to server 2008 r2 that will bring even more cool features for sccm osd /multicast)

you can use something like this: select distinct SMS_R_System.Name, SMS_R_System.SMSAssignedSites, SMS_R_System.IPAddresses, SMS_R_System.IPSubnets, SMS_R_System.OperatingSystemNameandVersion, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.LastLogonUserDomain, SMS_R_System.LastLogonUserName, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceId, SMS_R_System.NetbiosName, SMS_G_System_SoftwareFile.FilePath from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileName = "msascui.exe" and SMS_R_System.OperatingSystemNameandVersion = "Microsoft Windows NT Workstation 6.0" i think definition updates are better handled with software update mechnism then regular packages

is the client/clients geting any other advertisements? do you see hardware/software inventory up to date on those client/clients? are you sure the package is "installed" on the d.point you sent it to? is this d.point protected? is the client inside those protected boundaries?

dns is the first thing to check if your geting this on all workstations if you are seing this on a few check their domain membership.

check this out for diffrent hals on the same image no scripts needed just change the wim index http://myitforum.com/cs2/blogs/cnackers/ar...k-sequence.aspx

Hi just wondering if anyone seen this thing i build a image for toshiba m9 and added all drivers and all that and when building the task sequence i was able to choose the mass storage device to load and all went great. now i tried to do the same thing on a toshiba m3 and also for hp dc5700 i downloaded all drivers imported them and send the package out to dp's. but when i go to choose what mass storage device will load for the image its gray ,when i click the load... it doesnt "see" the mass storage devices(its just intel inf files nothing special) and the thing is i verified the driver is in sccm,i mean i see it and its in the package also but cannot be selected for some reason. any idea? (since i dont have much time i think the best solution is just to use nlite to integrate the latest intel matrix to the source files and create the image in vmware,i have found that this works every time no matter if its a dc5700 a toshiba m9,basicly not relying on mass storage in sccm for boot just for pnp of other devices)

i would never reinstall or fresh install asite UNLESS there is database corruption anything else can be fixed. this way you dont loose client data/application deployment data and configurations. you need to see what errors you are getting and eliminate them one by one. thats my opinion anyway.

quick question when you manually install from that cd and enter the key does it activate(no internet)? it should activate without internet connection,if it doesnt then something is missing, my guess is that the oem(dell) certificate is missing(although it shouldnt if u r using dell cd) check to see if the certificate is inside the windows directory again oem's do not activate online.

hey your management point isnt working almost for sure(error 500 on http for smp) check iis and its configuration and pre-requesities so you need to look at that before anything else otherwise no policies will go down to the clients. you can check many logs but pay attention to mpcontrol.log on the server to get the exact error(probably 500 there)

small question why is the content version at 43? is this package on auto update content? client thinks there is newer version and is waiting to download it "Content version for program AdbeRdr package JED00007 has been changed to 21" "Cancel content request for program AdbeRdr package JED00007 as content version has changed" client is asking for content version that doesnt exists. could you update policy wait 10min and post all client logs?(zip)

the logs are from server pull policy from client and send the client logs in zip so we can see whats up on client and why it doesnt have the files locally

hey there just asmall hints you know oem activation doesnt really go anywhere(internet) it activates using the oem certificate matching hardware and serial. if those three arent there it will try online and reach the limit for one key. so if you reimage oem's make sure the certificate for the oem is there and disconnect from internet(you dont have to but just for test) it should activate automaticly if the three things are right(hardware/certificate/serial) check here for one way to backup the oem certificates: http://www.vdhout.nl/20080301/

thanks man for lightning speed reply will try it awesome site again just checked ronnies blog amazing stuff thanks again

Hi just wondering if someone did this thing before instead of trying all options. i captured an image and uploaded it to the server(sccm 2007) all seems good and i can apply it. it applies but the resolution stays at default. how can i change that? sysprep.inf or unattended.txt (i dont really need anything else to be customized other then this) anybody tried this? thanks in advance