teamfox201

Have you looked at this link? If so, what exactly is your issue / question? http://technet.microsoft.com/en-US/library/dn145038.aspx

The tool itself uses RAMDISK to run and I know that the SCCM boot image is also RAMDISK but it does not seem to be as easy as copying the files and running them. This is the tool i'm trying to get working: http://www.dell.com/support/drivers/us/en/19/DriverDetails?driverId=GTW03

Hello, I have a ~8 mb bootable iso that contains the Dell diagnostics tools for laptops. Is it possible to somehow use this iso to boot into the diagnostic tool from PXE using SCCM 2007?

How do you make this work in WinPE and HKCU?

When we swap we decommission the old task sequence and put a new one into production. Creating the new TS generates a new ID but we use the old advertisement and just point it to the new TS. Is there a way to clean it up without losing all the records? Or would that require messing with the sql database.

We swap out our task sequence every 3-4 week's to add updates . Do the advertisements need to be recreated?

How can I clean the OSD report that shows which and how many systems successfully imaged, are still running , failed, etc. There are systems on the still running report that are 2+ months old. Obviously they either finished or failed but I need to clean up the report.

Hello, I am trying to create an ISO from my offline media so that we can copy it to a central location and people can make their own bootable USB. The problem is that our complete offline image is almost 11GB and when you create a ISO through the SCCM console, it breaks the ISO up into 8.5 GB and another 2.x GB. There inst an option to leave the whole thing in tact. How can I get only one full sized ISO that others can burn without having to create a bootable USB through the Console itself or does anyone have any programs that I can convert my working offline USB into a bootable ISO? Thanks!

And the systems you are sending these advertisements to show as Approved and Client Yes in the console?

Hello, Sometimes a working package in SCCM stops working and we have to recreate the package. When we do that , we have to copy the users from the old collection to the new collection and since we have a new package and new advertisement they get a popup that software is available. Is there a way to disable these popups for the people that already installed the software in that collection?

By default if you are using USMT 4 it should migrate that over. http://technet.microsoft.com/en-us/library/dd560792(WS.10) To retain the pst file names I use migapp.xml and migdocs.xml instead of miguser.xml

Hello, it looks like they are being migrated but not to the right place but instead they are going to c:\dbis. . . Do those partition/mapping letters exist when you are running loadstate?

Hello, I have some questions about USMT and config.xml i was hoping someone can help me out. My understanding of using a Config.xml file is that I need one for systems going from XP to Windows 7 and another one for Windows 7 to Windows 7 since the DlManifests are different on the two OS's. So if I run Scanstate.exe on a XP machine, using ConfigXP.xml after upgrading the OS to Windows 7 i have to run the LoadState.exe using the ConfigXP.xml file? And the same goes for Windows 7 reimages. I use ScanState.exe with the ConfigW7.xml and restore using LoadState.exe with the ConfigW7.xml. If the above is true, what is the best way to automate if ScanState.exe was ran from a XP machine, to use the correct Config.XML file once the machine is upgraded to Windows 7? Thank you.

The last time I had an issue like this with that error message, was because the drive was not formatted as NTFS. If your Windows 7 wim file is over 4GB you need to make sure the drive is formatted as NTFS not FAT32.

I know this is old, but is there an answer?