Jump to content

cluberti

Patron
  • Posts

    11,045
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

Posts posted by cluberti

  1. Jellybean does indeed find a product key, but that's the OEM's master key for imaging, and isn't used for activation at all (rather the certificates in the OS for auto-activation against the BIOS instead). You will have to use the product key from the COA sticker affixed to the laptop itself to actually input a key you can activate, as previous posters have mentioned, or you will have to restore the old image and back up the auto-activation information to be restored during a restore of an image onto that machine. Instructions on how to back up / restore OEM activation can be found elsewhere on this board.

  2. Only superficially; It seems an order of magnitude more involved and seems to depend on SCCM for a lot of stuff.

    From what I've gleaned so far, the entire deployment procedure would need to be changed from the PXE server setup onward :/

    I don't mind admitting that I find the whole thing quite daunting :unsure:

    Actually, SCCM relies on MDT for some things (if integration is enabled), but MDT itself is completely stand-alone. However, it's ok to find it daunting :). I'd still recommend using MDT to build your answer files and task sequences, and boot to the MDT boot images from a PXE server or off of a bootable USB key rather than do things manually.

  3. Interesting. Could be a package incompat issue (using packages just applies all packages offline and lets the OS decide during specialize which updates to apply and which to discard). You will want to start by checking each package in your list and make sure you're not applying packages that update the same files, or switch to online package updating with WSUS.

  4. Patching your image is ending up with packages having issues updating the WinSXS folder structure, and ultimately failing with E_ACCESSDENIED. What happens if, for instance, you simply download KB2487335, place it (and only it) in the Updates folder, and attempt to re-deploy your WIM file (so it should be pushing the Win7 SP1 image from the MSDN source with only that package) using a new stock task sequence with no changes whatsoever?

  5. I would doubt that by 2014 it will be any larger than about 25% other than asia (piracy, mostly), given the trends even this year in 2011. Microsoft usually keeps updates and such available for at least 5 years after an OS officially hits End Of Life, although this will be the first OS that required activation to hit EOL, so I suppose we'll see. I would expect activation servers to be online for a few years after 2014, and 2019 (given their previous behavior with updates and articles, etc) seems like a reasonable time. If you can still find hardware and drivers to install XP onto properly in 2019, I'd be very surprised.

    I guess "we'll see" is the answer, but Microsoft no longer supporting the OS but requiring activation will be the interesting bit once they start taking things down. Perhaps a hotfix to disable WPA is in the cards?

  6. Given acquiring Windows XP nowadays isn't possible in the retail or OEM channels without a separate agreement from Microsoft (and OEM and volume versions of XP don't activate with Microsoft anyway), the actual amount of XP activations nowadays is probably a very small number. Not sure about when or if they'll turn them off, so to speak, but I think the quip above about DOS 6.0 is probably pretty accurate ;).

  7. Even at home I have two monitors attached to my desktop - one 21" monitor is in portrait mode (very tall, not very wide in this format) and running Outlook (very useful to have a tall monitor for email with the reading pane at the bottom); one 30" monitor is in landscape mode where most of my other work is done. Email is critical to my day-to-day, and as such it occupies one monitor entirely.

  8. +1 - if you have an Acer that came with Windows, the product key is in a sticker affixed to the case or the power supply (some Acer laptops had the CoA / PID stuck on the power brick, and Samsung has been doing this lately too). That is your option, short of purchasing a copy of Windows.

  9. Disabling IPv6 is unsupported by Microsoft, and (as you've found with homegroup, some things will not work right (or at all) with it disabled. A better approach is to disable teredo, which is the component most people have issues with.

  10. Recreate the profile path and shares (as configured in group policy) on a server with the same name (for offline files cache reasons), and make sure that the user has modify access to the share, and NTFS change control on all subfolders and files in their profile directory. This is (basically) the way policy creates the folder structure when a user first logs onto the domain with a roaming profile, so this is about all you need to do.

    As to it being a DC, make sure it holds no FSMO roles when you dcpromo it down (and you've allowed for replication), and rebuild it with the same name (removing the old computer object from AD before rebuilding). Name it the same, and rejoin the domain and re-dcpromo (if you still want it to be a DC).

×
×
  • Create New...