Jump to content


brianincolorado

Established Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About brianincolorado

  • Rank
    Newbie
  1. We have now also disabled PXE from the DP's which also disables WDS. Once this was completed, the server was reboot and PXE along with WDS were enabled. However this did not solve the issue. Our environment is as follows: SCCM 2012 running on VMware One Primary server 5 regionalized DP's (same problem from all DP's) We need to restore this functionality as we have 50 new machines to deploy in February. At this point, we have escalated a ticket to Microsoft under our Software Assurance contract but have not received a follow up from their technicians. Frankly, I am more confident in receiving a solution from this forum anyway. Any help would be appreciated.
  2. I am strugging to get OSD to work from PXE after the processes suddently stopped working for all of your hardware models. What occurs is after PXE booting, the initial download of the .wim is completed and Windows PE briefly loads. Shortly after loading Network Connections, the system reboots. To identify/resolve the issue the following steps have been completed: F8 before the reboot occurs shows the computer is not getting an IP The x86 boot image in SCCM appears to have gotten corrupted as we were unable to add new drivers (although the existing drivers always worked before this issues started) Restored the default boot image from \\server\SMS_DE1\OSD\boot\i386\boot.wim Added "all" drivers categorized as NET & HDC (i know this is not necessary but wanted to ensure correct driver was included) Distributed to all DP's Uninstalled/Installed Windows AIK 2.0 Deleted all drivers from SCCM and reimported along with creating new Driver Packages Issue occuring for all computer models SCCM server reboot I have attached smsts.log files showing the error. When viewing properties of the x86 Boot Image, all of the required drivers are listed and the Content Status is showing a current timestamp signaling the DP's should have the correct file version. There may be some steps I did not include in this post so just let me know what else you need to help identify the issue. Thank you ALL for your help as I am quite frustrated with this issue and am open to suggestions. smsts.log
  3. Is there anyone out there deploying custom fonts for Office 2010 that can share some insight. Much appreciated!
  4. We are running a script which copies the template files the the %appdata\microsoft\template folder. The problem is Word 2010 renames the existing file to normal.old upon first launch regardless if the existing .dotm file was created in 2010. Therefore, the registry entry which I referenced earlier must be added to prevent Word from renaming the existing template. I need to know how to add a registry key for ALL USERS that log into a machine. Can this be done in my Core Image and if so how? Thanks,
  5. Thank you for the response however this does not work per testing and sorry I did not include this in my initial post. First, Office 2010 is part of the Core Image therefore the Office Customization Tool is not a factor in OSD. However, we are also testing upgrading Office 2007 to 2010 and have tried the method you describe with no luck. For the upgrade to work, we just first deploy a script that adds ("HKCU\Software\Microsoft\Office\14.0\Word\Options\MigrateNormalOnFirstBoot", 1, "REG_DWORD"), and then the Office 2010 setup.exe is ran. This method DOES work for an upgrade. We are having problems deploying the core image which includes Office 2010 along with the custom fonts
  6. Thank you for the response however this does not work per testing and sorry I did not include this in my initial post. First, Office 2010 is part of the Core Image therefore the Office Customization Tool is not a factor in OSD. However, we are also testing upgrading Office 2007 to 2010 and have tried the method you describe with no luck. For the upgrade to work, we just first deploy a script that adds ("HKCU\Software\Microsoft\Office\14.0\Word\Options\MigrateNormalOnFirstBoot", 1, "REG_DWORD"), and then the Office 2010 setup.exe is ran. This method DOES work for an upgrade. We are having problems deploying the core image which includes Office 2010 along with the custom fonts.
  7. First, thank you all for putting together such a complete forum on SCCM and related topics as they have been essential in my daily duties. We are attempting to deploy custom normal.dotm, blank.potx, and normalemail.dotm files which are configured for Verdana font. So far, the following items have been completed: 1. Created customized W7 Image on VMWare 2. Installed Office 2010 SP1 with custom (normal.dotm, blank.potx, normalemail.dotm) located at c:\users\%username%\appdata\microsoft\templates 3. Ran Sysprep by running following .CMD <C:\windows\system32\sysprep\sysprep.exe /oobe /shutdown /generalize /unattend:C:\windows\system32\sysprep\unattend.xml> 4. Captured .wim using ImageX 5. Deploying OSD via SCCM 2012 All customizations are deployed properly to all users who login except for the Office Template files (CopyProfile=True in unattended.xml). The path c:\users\%username%\appdata\microsoft\temlates is not copied to each user who logs in. To rectify this, we added a RunOnce registry entry on our Reference Machine to create the path and copy the necessary files. We thought this was the fix, but once Word is launched for the first time it renames the normal.dotm file to .old. Microsoft has published the following article to address this issue (http://support.microsoft.com/kb/2408845) which does work on a per user basis. However, we need to ensure this registry entry is present for any user who logs into the computer. At this point, we have tried also using the RunOnce function to import the reg key ("HKCU\Software\Microsoft\Office\14.0\Word\Options\MigrateNormalOnFirstBoot", 1, "REG_DWORD") but this has not worked in adding the Reg entry for each user. Can we get some guidance on how to best deploy custom normal.dotm, blank.potx, and normalemail.dotm during OSD with SCCM 2012. Thank you all!
  8. First, thank you all for putting together such a complete forum on SCCM and related topics as they have been essential in my daily duties. We are attempting to deploy custom normal.dotm, blank.potx, and normalemail.dotm files which are configured for Verdana font. So far, the following items have been completed: 1. Created customized W7 Image on VMWare 2. Installed Office 2010 SP1 with custom (normal.dotm, blank.potx, normalemail.dotm) located at c:\users\%username%\appdata\microsoft\templates 3. Ran Sysprep by running following .CMD <C:\windows\system32\sysprep\sysprep.exe /oobe /shutdown /generalize /unattend:C:\windows\system32\sysprep\unattend.xml> 4. Captured .wim using ImageX 5. Deploying OSD via SCCM 2012 All customizations are deployed properly to all users who login except for the Office Template files (CopyProfile=True in unattended.xml). The path c:\users\%username%\appdata\microsoft\temlates is not copied to each user who logs in. To rectify this, we added a RunOnce registry entry on our Reference Machine to create the path and copy the necessary files. We thought this was the fix, but once Word is launched for the first time it renames the normal.dotm file to .old. Microsoft has published the following article to address this issue (http://support.microsoft.com/kb/2408845) which does work on a per user basis. However, we need to ensure this registry entry is present for any user who logs into the computer. At this point, we have tried also using the RunOnce function to import the reg key ("HKCU\Software\Microsoft\Office\14.0\Word\Options\MigrateNormalOnFirstBoot", 1, "REG_DWORD") but this has not worked in adding the Reg entry for each user. Can we get some guidance on how to best deploy custom normal.dotm, blank.potx, and normalemail.dotm during OSD with SCCM 2012. Thank you all!
×
×
  • Create New...