Jump to content

cluberti

Patron
  • Posts

    11,045
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

Everything posted by cluberti

  1. Try this, let me know if it works: <Configuration Product="ProPlus"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> <PIDKEY Value="1234567890123456789012345" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <Setting Id="AUTO_ACTIVATE" Value="1" /> <USERNAME Value="User" /> <COMPANYNAME Value="Demo" /> </Configuration> I believe you have a typo in your Configuration Product line, and you don't really need the distribution line either unless you're chaining installations.
  2. Can you be more explicit in what exactly you're doing, what you've tried, and what the results have been? I know you know what those are, as you're doing them, but we won't know that . If you could just expound on your post, we might be able to start helping.
  3. I've never been a fan of the company culture he fosters, but that doesn't mean greatness and genius weren't there - he had both in spades. The world will indeed be a different place without a Steve Jobs showing us what kinds of things are possible through technology and design.
  4. It may have, but given it's not technically valid for retail builds, it breaking with a service pack isn't entirely odd either, really.
  5. You either give rights to a file, or you don't - what you could do is give users "Special" rights, and allow them write access but not list access - this would allow them to upload files but not see anything in the share. However, that doesn't preclude them from simply overwriting what they've put there with another file, because rights are static. This would require custom scripting, event triggering, and probably constant administration.
  6. vLite downloads just fine from the links on http://www.vlite.net.
  7. From the site (emphasis mine): Is that what you mean?
  8. Also note that for users, in general, external access via IMAP and POP is disabled. You may have to go to the properites of that user account in the Exchange console and enable their access to the server via those protocols.
  9. Given almost every component other than the disk has improved immensely since the late 70s/early 80s, and hard disk technology has not, in general the easiest bottleneck to find and remove is the hard disk (replace it with an SSD and watch the CPU become the bottleneck ).
  10. It will depend on where Chrome is storing the data. The installation itself (if using the web installer) goes into the user's %AppData% folder, but not everything stored here will migrate to a new profile even with CopyProfile set. I don't know specifically where the homepage data is stored for Chrome, but it would be interesting to see a before and after to verify it's not backed up.
  11. Happy getting older and wiser day to you both .
  12. http://www.cluberti.com/blog/2011/06/23/mdt-for-the-smaller-guys-part-1/ It's for Hyper-V, but obviously easily followed for any other virtualization platform.
  13. cluberti

    MSI's

    It used to, back in the pre-Win9x days (<=Win 3.x), but with the advent of the registry and it's APIs and the Microsoft Installer engine, it didn't make sense to use something less powerful, harder to audit, and less secure than the registry for storing things like that. Also, the .MSI files are kept around in the event the application needs to be repaired (or needs to repair itself) so that the app can be repaired, reinstalled, or uninstalled without having the original source media available. 270MB isn't really all that much space, in the long run, but deleting those files is safe. Just be aware that anything that triggers the MSI engine to repair or remove an installed application that was installed via the MSI will prompt for the installation media location and installation files as necessary.
  14. You turn off first run - that policy sets the registry setting to work around the issue .
  15. If you slipstream the IE9 .cab (from the MSU), you will have the issue (it's a known issue). If you install it on a running system (either via the .exe, or the .msu), you will not have the issue.
  16. Seems like Microsoft's page on the matter already answers your questions.
  17. If one has download or media access to a volume-licensed source of any Microsoft product, then they should have access to unmodified sources back to at least the last supported version (and as is the case with OSes, all the way back to the RTM ISO release). If you or your friend created the original XPSP2 source via nLite (and from what you've mentioned happens, it would seem likely - those files would only be missing if some tool removed them to "remove the bloat"...), you *cannot* with any sort of reliability or repeatability edit a source that has already been nLite'ed without reverting back to the original source, and as such was never supported or tested by nuhi when writing the tool. I'm going to save you some time, in as polite a way as I can - you would be best served going back to an original RTM source, and slipstreaming SP3 into it. After that, you can use nLite to go back and use that source (MAKE A BACKUP) to automate the installation. That XPSP2 installation you have is locked in stone, for all intents and purposes, and you'd do well to stop at that and move on. Lastly, if your father's company does indeed have a license to XP (and includes the machines you're using it on as valid license counts), then you will find he will indeed have access to download an XP source (in fact, an XP SP3 source ISO as well, which would probably be best). I know your goal is to save the pre-existing installation media, but you're just not going to be able to do it.
  18. Basically, no. http://www.intel.com/support/ssdc/hpssd/sb/CS-029623.htm#5
  19. Yup, it's either connectivity (physical) to the disk (cable or power), or the disk itself is going bad. Good luck, and let us know how it turns out.
  20. Why would you go through the hassle of installing to a VM, installing IE9 and updates, sysprep/capturing it, then redeploying it when you can just slipstream it offline and add a reg hack? Seems like a lot of work to avoid adding one single registry DWORD...
  21. You can't edit the WIM files like you can Vista or Win7 (adding things offline, servicing, etc). An XP install is locked once sysprep'ed, but if you mean mount it and add or remove files, edit registry, etc, then yes. As to local policy, use Security Compliance Manager (works for XP SP3 and higher) to create and apply local policy settings.
  22. It appears to be a known issue, as I contacted Microsoft about this very issue. Unfortunately, the workaround for now is indeed to apply a registry hack to disable it. I have no idea if they're going to be able to fix it or not. As to it working with MDT, that is because it is integrated differently (online) versus off - apparently there's some sort of issue with integrating it offline.
  23. Might want to run process monitor on that machine while installing the driver to see what file can't be found.
  24. Interesting. So if it's all users and all servers on that machine, it would seem to be machine-based. Just to verify, users on other machines against these file shares aren't having these issues?
  25. Hmmm, that should work fine without anything special. Next question - if you add favorites using the Add Favorite button, does it add it (should show up in %userprofile% in their favorites folder)?
×
×
  • Create New...