Scotty_E

Hi Forum, I have just received a new HP laptop with an Intel SSDSA1M160G2 SSD drive installed. I use SCCM SP2 to deploy sysprepd Windows XP images (WIN7 soon). Using my usual SSD DISKPART script results in an 'Unmountable Boot Volume' error after the sysprep mini setup. I can also see that the disk has been changed from NTFS to RAW. Easy your thinking, its the UBER WINPE bug.. I wish! I have already ensured that the DISKPART compatibility mode is set to true, and as a backup, am applying the required registry settings to WINPE as outlined in http://support.microsoft.com/kb/931760/en-au. What I have narrowed it down to is the DISKPART align parameter. If I use the same DISKPART commands to create my volume without the align parameter, the volume is created and the Windows XP Deployment process completes as expected. If I add an align parameter into the DISKPART create partition line (I have tried align=64 align=128 align=2048) Windows XP ends with the Unmountable Boot Volume BSOD. There are alot of posts online regarding the importance of correct alignment of a volume for Windows XP and SSD, which is why I have added the additional step. My DISKPART script is below. SELECT DISK 0 CLEAN SELECT DISK 0 CREATE PARTITION primary align=128 noerr SELECT PARTITION 1 ACTIVE SELECT PARTITION 1 FORMAT FS=NTFS quick noerr SELECT PARTITION 1 ASSIGN Letter=C noerr The above has worked fine for other laptops with SSD drives installed (non Intel SSDs) Has anyone had any experience aligning the new Intel G2 SSD drives? I am wondering if the Intels need a particular align value or something obvious I am missing. I would really like to prepare these partitions properly to get the maximum performance out of the machine until we move to WIN7 later this year. Thanks For Reading..

Hi All, I have started planning and testing our upgrade from Office 2003 to Office 2007. I have followed the Microsoft documented deployment guide and created my MSP file, and added the SP2 updates into the updates folder. Upgrade testing is going well. Everything installs as expected, and my custom settings from the MSP file are applied. The problem that I have is that the upgrade is taking what I perceive to be a very log time! (Over an hour). It doesn't seem to make a difference if I perform the upgrade on new hardware either. This makes me believe that there is an issue, or that an hour to perform the upgrade is normal. (I hope not) I am running the test upgrades from SCCM on 4 test clients. These test clients already have the full suite of Office 2003 SP2 installed, so as part of the deployment it removes all previous Office 2003 applications as well. From what I can tell, it seems to stall for quite sometime at the log location of "Determining ARP entry registry values." It then Takes an hour to do the below... </LogSnip> Executing chained package: OfficeMUI.en-us 02/26/2010 18:09:31 Installing chained package: OfficeMUI.en-us PERF: TickCount=1587593 Name=Verify MSI local install source Description=Begin function OSE is detected as a registered service. Service binary is reported at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE OSE service binary is detected at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE OSE is avaliable at C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE This OSE has version: 11.0.5525.0000. Skip using this version of OSE because its version is too low. Running OSE version 12.0.4518.1014 OSE is detected as a registered service. Service binary is reported at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE OSE service binary is detected at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE OSE is avaliable at C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE This OSE has version: 11.0.5525.0000. Skip using this version of OSE because its version is too low. Running OSE version 12.0.4518.1014 LIS: wait for package "{90120000-0115-0409-0000-0000000FF1CE}" to complete caching LIS: package "{90120000-0115-0409-0000-0000000FF1CE}" caching completed PERF: TickCount=4835562 Name=Completed verify local install source Description=End function Catalyst Package Install... Package: OfficeMUI.en-us File: C:\MSOCache\All Users\{90120000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi Command Line: ADDLOCAL=MetricConverterIntl_1033,AlwaysInstalledIntl_1033,MSTagPluginStockFilesIntl_1033,VBAHelpFilesIntl_1033,GraphicsFiltersCGMFilesIntl_1033,EquationEditorFilesIntl_1033,GraphicsFiltersEPSFilesIntl_1033,CAGCat10Intl_1033,MSTagPluginNamesFilesIntl_1033,MsoInstalledPackagesScopedIntl_1033,WebDiscussFilesIntl_1033,CAGOffice10Intl_1033,OISFilesIntl_1033,HTMLSourceEditingIntl_1033,CAGFilesIntl_1033,MSPHELPIntl_1033,WISPHiddenIntl_1033,AceFilesIntl_1033,SetLanguageFilesIntl_1033,OSetupControllerIntl_1033,WebDebuggingIntl_1033,XDOCSEditorFilesIntl_1033,MSOfficeDocumentImagingIntl_1033,SetupControllerFiles,ClviewFilesIntl_1033,ProductNonBootFilesIntl_1033,MSTagPluginPlacesFiles_1033,TCWP5FilesIntl_1033,AceReplIntl_1033,ProductFilesIntl_1033,GraphHelpFilesIntl_1033,Gimme_OnDemandData,GraphicsFiltersWPGFilesIntl_1033,TCWP6FilesIntl_1033,GraphicsFiltersGIFFilesIntl_1033,GRAPHFilesIntl_1033,MSTagPluginDateFilesIntl_1033,WebDriveFilesIntl_1033,LISTFilesIntl_1033,MsInfoFilesIntl_1033,TCRecoverFilesIntl_1033,SetupXmlFiles,TOOLSFilesIntl_1033,VisioPreviewerIntl_1033,GraphicsFiltersPNGFilesIntl_1033,MSSOAP3Intl_1033,OfficeVBAHelpIntlHiddenIntl_1033,GraphicsFiltersPICTFilesIntl_1033,OfficeDigitalSFilesIntl_1033,VBAFilesIntl_1033,GraphicsFiltersJPEGFilesIntl_1033,QueryFilesIntl_1033,SetLanguageHelpFilesIntl_1033 ARPENTRY_HELPTELEPHONE="" ARPENTRY_NOREMOVE="#0" ARPENTRY_CONTACT="" ARPENTRY_HELPLINK="" ARPENTRY_NOREPAIR="#1" ARPENTRY_SHELLUITRANSFORMLANGUAGE="en-US" ARPENTRY_SKUCOMPONENTS="[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\InfoPath.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Proofing.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Publisher.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Access.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Office.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\PowerPoint.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Rosebud.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Excel.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Outlook.en-us\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\PROPLUS\setup.xml[~]C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Word.en-us\setup.xml[~]" ARPENTRY_URLINFOABOUT="" HIDEUPDATEUI="True" ARPENTRY_CACHELOCATION="C:\MSOCache\All Users" COMPANYNAME="XXXXXXXX" ACCEPTEDEULA="1" ARPENTRY_MODIFYPATH="""C:\Program Files\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\setup.exe"" /modify PROPLUS /dll OSETUP.DLL" ARPENTRY_PACKAGEIDS="[~]OfficeMUI.en-us[~]OfficeMUISet.en-us[~]ExcelMUI.en-us[~]OutlookMUI.en-us[~]PowerPointMUI.en-us[~]RosebudMUI.en-us[~]InfoPathMUI.en-us[~]Proof.es-es[~]Proof.fr-fr[~]Proof.en-us[~]Proofing.en-us[~]PublisherMUI.en-us[~]WordMUI.en-us[~]AccessMUI.en-us[~]AccessMUISet.en-us[~]ProPlusWW[~]AccessMUISet.en-us[~]AccessMUI.en-us[~]WordMUI.en-us[~]PublisherMUI.en-us[~]Proofing.en-us[~]Proof.en-us[~]Proof.fr-fr[~]Proof.es-es[~]InfoPathMUI.en-us[~]RosebudMUI.en-us[~]PowerPointMUI.en-us[~]OutlookMUI.en-us[~]ExcelMUI.en-us[~]OfficeMUISet.en-us[~]OfficeMUI.en-us[~]" ARPENTRY_PRODUCTCODES="[~]{90120000-006E-0409-0000-0000000FF1CE}[~]{90120000-0115-0409-0000-0000000FF1CE}[~]{90120000-0016-0409-0000-0000000FF1CE}[~]{90120000-001A-0409-0000-0000000FF1CE}[~]{90120000-0018-0409-0000-0000000FF1CE}[~]{90120000-0010-0409-0000-0000000FF1CE}[~]{90120000-0044-0409-0000-0000000FF1CE}[~]{90120000-001F-0C0A-0000-0000000FF1CE}[~]{90120000-001F-040C-0000-0000000FF1CE}[~]{90120000-001F-0409-0000-0000000FF1CE}[~]{90120000-002C-0409-0000-0000000FF1CE}[~]{90120000-0019-0409-0000-0000000FF1CE}[~]{90120000-001B-0409 PERF: TickCount=4835953 Name=MsiPackage::Install Description=Calling OMsiInstaller::InstallProduct for package file "C:\MSOCache\All Users\{90120000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi" PERF: TickCount=4867703 Name=MsiPackage::Install Description=Returned from OMsiInstaller::InstallProduct Successfully installed package: OfficeMUI.en-us path:C:\MSOCache\All Users\{90120000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi Executing chained package: OfficeMUISet.en-us 02/26/2010 19:04:11 Installing chained package: OfficeMUISet.en-us </LogSnip> If it completes the above, It installs SP2 which takes about 5 mins. Has anyone else performed an Office 2003 to Office 2007 upgrade -If so how long did the upgrade take from start to finish? Can anyone with previous experience with this upgrade offer any suggestions to try and speed things up a little? Thanks, - Scott.