Jump to content

dijuremo

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About dijuremo

dijuremo's Achievements

0

Reputation

  1. I did *not* integrate IE7, only windows updates since I was trying to troubleshoot the issue and started only with the updates. After fixing the registry permissions on they key mentioned in your post, everything worked correctly for me. So this must be a bug in nlite 1.2.1. I have listed the correct permissions in your post. However, I am also listing them here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer Administrators - Full Control System - Full Control Everyone - Read When the permissions above are set, remember to propagate them down to the childs, otherwise, you will still have problems. This permission change fixes my Office 2003 install issues.
  2. This is *not* just related to IE7. I slipstreamed only windows updates using nlite and found the same problem while running office for a new user because it needs to run the msi installer the first time any office application launches (see my posting). It should be a bug in the nlite slipstreaming process which does not change the registry key permissions on that key. I just checked another system that was installed by hand and the default permissions on that registry key should be: Administrators - Full Control System - Full Control Everyone - Read When changing this permissions on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer make sure you set them to propagate down by selecting the check box that reads: "Replace permission entries on all child objects ..." The permissions after using nlite patched files to install a new machine in unattended mode are: Administrators - Special (mostly read permissions) System - Full Control There are no permissions for "Everyone" as you mention. After changing the permissions (remember to propagate them to the child) and rebooting, I was able to log in to the machine with a new user account that had no administrator rights and launch Word for the first time without getting errors as before. The issue is not just IE7 related, must be an nlite 1.2.1 bug. Thanks for finding the problem, you made my day.
  3. From the event viewer: Event Type: Warning Event Source: MsiInstaller Event Category: None Event ID: 1001 Date: 11/10/2006 Time: 2:42:42 PM User: OEM-274CE6D1053\dijuremo Computer: OEM-274CE6D1053 Description: Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature 'WORDFiles' failed during request for component '{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}' For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: .NET Runtime Event Category: None Event ID: 0 Date: 11/10/2006 Time: 2:42:42 PM User: N/A Computer: OEM-274CE6D1053 Description: The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to open shim database version registry key - v2.0.50727.00000. Event Type: Error Event Source: MsiInstaller Event Category: None Event ID: 10005 Date: 11/10/2006 Time: 2:43:01 PM User: OEM-274CE6D1053\dijuremo Computer: OEM-274CE6D1053 Description: Product: Microsoft Office Professional Edition 2003 -- Error 2503. An internal error has occurred. ( ) Contact your Information Technology department for assistance. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 7b 39 30 31 31 30 34 30 {9011040 0008: 39 2d 36 30 30 30 2d 31 9-6000-1 0010: 31 44 33 2d 38 43 46 45 1D3-8CFE 0018: 2d 30 31 35 30 30 34 38 -0150048 0020: 33 38 33 43 39 7d 383C9} Event Type: Error Event Source: MsiInstaller Event Category: None Event ID: 10005 Date: 11/10/2006 Time: 2:43:02 PM User: OEM-274CE6D1053\dijuremo Computer: OEM-274CE6D1053 Description: Product: Microsoft Office Professional Edition 2003 -- Error 2502. An internal error has occurred. ( ) Contact your Information Technology department for assistance. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 7b 39 30 31 31 30 34 30 {9011040 0008: 39 2d 36 30 30 30 2d 31 9-6000-1 0010: 31 44 33 2d 38 43 46 45 1D3-8CFE 0018: 2d 30 31 35 30 30 34 38 -0150048 0020: 33 38 33 43 39 7d 383C9} Event Type: Information Event Source: MsiInstaller Event Category: None Event ID: 11729 Date: 11/10/2006 Time: 2:43:02 PM User: OEM-274CE6D1053\dijuremo Computer: OEM-274CE6D1053 Description: Product: Microsoft Office Professional Edition 2003 -- Configuration failed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 7b 39 30 31 31 30 34 30 {9011040 0008: 39 2d 36 30 30 30 2d 31 9-6000-1 0010: 31 44 33 2d 38 43 46 45 1D3-8CFE 0018: 2d 30 31 35 30 30 34 38 -0150048 0020: 33 38 33 43 39 7d 383C9} The file you requested from the nlite forlder: Last_Session.ini
  4. Nope, The date and time in the machine are correct and the KB seems to be only for Office XP and 2000. I am using 2003. But thanks for trying.
  5. Could anyone else confirm if this happens to you as well? I basically used nlite to slipstream most of the windows updates and then installed office from and install point. The steps I took to accomplish this are shown below. 1. Copied all the files to the folder called XPproVL 2. Used nlite to apply most of the updates which can be slipstreamed (listed at the end of the post) 3. Installed a machine in unattended mode and applied the missing updates using Microsoft Update. 4. Installed Office 2003 from an Administrative installation point. The Admin point was created according to instructions from: Office AIP howto 5. Office Applications run correctly for Administrator. 6. Created a new user and logged in as that user. 7. Launch MS Word, the Office setup part starts where it asks the new user for their name and initials, but fails with the following errors: I hit ok and then get I hit ok and then get I am sure the office admin point is fine since I installed another system by hand from the original cd, then applied all updates from the windows update website, installed office and had no problems while launching it for the first time with a new user that I created which is not administrator nor has administrator rights. Does anyone know how to fix this problem? ------- List of Windows updates integrated with nlite --------- Windows-KB909520-v1.000-x86-ENU.exe WindowsInstaller-KB893803-v2-x86.exe WindowsMedia-KB911564-x86-ENU.exe WindowsXP-KB873339-x86-ENU.exe WindowsXP-KB885626-v2-x86-enu.exe WindowsXP-KB885835-x86-ENU.exe WindowsXP-KB885836-x86-ENU.exe WindowsXP-KB886185-x86-enu.exe WindowsXP-KB887472-x86-enu.exe WindowsXP-KB888302-x86-ENU.exe WindowsXP-KB890046-x86-ENU.exe WindowsXP-KB890859-x86-ENU.exe WindowsXP-KB891781-x86-ENU.exe WindowsXP-KB893756-x86-ENU.exe WindowsXP-KB896344-v2-x86-ENU.exe WindowsXP-KB896358-x86-ENU.exe WindowsXP-KB896423-x86-ENU.exe WindowsXP-KB896424-x86-ENU.exe WindowsXP-KB896428-x86-ENU.exe WindowsXP-KB898461-x86-ENU.exe WindowsXP-KB899587-x86-ENU.exe WindowsXP-KB899589-x86-ENU.exe WindowsXP-KB899591-x86-ENU.exe WindowsXP-KB900485-v2-x86-ENU.exe WindowsXP-KB905414-x86-ENU.exe WindowsXP-KB905474-ENU-x86.exe WindowsXP-KB905749-x86-ENU.exe WindowsXP-KB908519-x86-ENU.exe WindowsXP-KB908531-v2-x86-ENU.exe WindowsXP-KB910437-x86-ENU.exe WindowsXP-KB911280-v2-x86-ENU.exe WindowsXP-KB911562-x86-ENU.exe WindowsXP-KB911567-x86-ENU.exe WindowsXP-KB911927-x86-ENU.exe WindowsXP-KB912817-v2-x86-ENU.exe WindowsXP-KB912919-x86-ENU.exe WindowsXP-KB913580-x86-ENU.exe WindowsXP-KB914388-x86-ENU.exe WindowsXP-KB914389-x86-ENU.exe WindowsXP-KB916595-x86-ENU.exe WindowsXP-KB917344-x86-ENU.exe WindowsXP-KB917422-x86-ENU.exe WindowsXP-KB917537-x86-ENU.exe WindowsXP-KB917953-x86-ENU.exe WindowsXP-KB918439-x86-ENU.exe WindowsXP-KB918899-x86-ENU.exe WindowsXP-KB919007-x86-ENU.exe WindowsXP-KB920214-x86-ENU.exe WindowsXP-KB920670-x86-ENU.exe WindowsXP-KB920683-x86-ENU.exe WindowsXP-KB920685-x86-ENU.exe WindowsXP-KB920872-x86-ENU.exe WindowsXP-KB921398-x86-ENU.exe WindowsXP-KB921883-x86-ENU.exe WindowsXP-KB922616-x86-ENU.exe WindowsXP-KB922819-x86-ENU.exe WindowsXP-KB923191-x86-ENU.exe WindowsXP-KB923414-x86-ENU.exe WindowsXP-KB924191-x86-ENU.exe WindowsXP-KB924496-x86-ENU.exe WindowsXP-KB925486-x86-ENU.exe ------- End List of Windows updates integrated with nlite ---------
  6. This is by design. Since most batch scripts reside in the file server (except the one used to mount the share), then at the beginning you do not have the other menus available because the Z: drive is not mounted yet and menus appear greyed out. When you go through step 1 which mounts the files, at the end you should see a message saying that the drive was succesfully mounted or that it failed. You will also be asked to reload the Nu2menu from: Go->System->Nu2menu->Reload Menu. The wait time for you to read this is 15 seconds. Do you think it is too short? Did you actually try mounting the file server files? You can confirm this by looking at the mount script in D:\DiegoStart\Pebuilder\plugins\DiegoStart\files\mount.bat which looks like: echo off color 0E net use Z: \\%DSSIP%\winsetup /user:installer if EXIST "Z:\scripts\hddsetup". ( echo "Diegostart server is now mounted on Z: from %DSSIP%" ) ELSE ( echo "Something is wrong Z: was not mounted" ) echo You must now reload the Nu2menu to enable all Diegostart features. echo "Click on: Go-->System-->Nu2menu-->Reload menu" echo This window will close in 15 seconds && sleep.exe 15 After reloading the Nu2menu all menus will be enabled as long as the network share was mounted correctly as the Z: drive. dijuremo
  7. Thanks for reporting the issue, I have commented out this update in slipstream.bat. I also made some other minor changes that can be found in the changelog of the DiegoStart website at: http://diegostart.dijuremo.org/index.php?title=Changelog A new release has been made 2.0.2 that includes the fixes: http://diegostart.dijuremo.org/images/latest.zip I am glad you guys find the site useful. All your comments, suggestions and requests are very welcome. dijuremo
  8. Hi all, After being given permission from one of the forum Moderators, I would like to announce to all of you DiegoStart. It is basically a methodology to perform unattended windows installations after mounting a windows share. Everything is installed from the network share including the OS. You can find out a lot more at the web site: http://diegostart.dijuremo.org I currently do not have forums configured in my website so I may ask the moderators if they are willing to open a DiegoStart forum section at MSFN if there are enough people who may want to discuss DiegoStart. I hope all of you like it and find it useful dijuremo.
×
×
  • Create New...