Jump to content

Bezalel

Member
  • Posts

    595
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Bezalel

  1. Here's Microsoft's official opinion.

    A refurbished PC is a computer system that has had substantial hardware modifications that may require a new operating system license — because the modifications have essentially created a "new" PC.

    Generally, you may upgrade or replace all of the hardware components on your customer's computer and the end user may maintain the license for the original Microsoft® OEM operating system software, with the exception of an upgrade or replacement of the motherboard.

    An upgrade of the motherboard is considered to result in a "new personal computer" to which Microsoft® OEM operating system software cannot be transferred from another computer. If the motherboard is upgraded or replaced for reasons other than a defect, then a new computer has been created and the license of new operating system software is required.

    Note that while Software Assurance can be transferred from one PC to another, the bootable operating system may not be transferred from one PC to another, regardless of whether the PC has Software Assurance.

    If the motherboard is replaced because it is defective, you do NOT need to acquire a new operating system license for the PC.

    The reason for this licensing rule primarily relates to the end-user license agreement (EULA) and the support of the software covered by that EULA. The EULA is a set of usage rights granted to the end-user by the PC manufacturer and relates only to rights for that software as installed on that particular PC. The System Builder is required to support the software on that individual PC. Understanding that end users, over time, upgrade their PC with different components, Microsoft needed to have one base component "left standing" that would still define that original PC. Since the motherboard contains the CPU and is the "heart and soul" of the PC, when the motherboard is replaced (for reasons other than defect) a new PC is essentially created. The original System Builder, therefore, can not be expected to support this new PC that they in effect, did not manufacture.

  2. Here is a quote from a page on the MS OEM site:

    A refurbished PC is a computer system that has had substantial hardware modifications that may require a new operating system license — because the modifications have essentially created a "new" PC.

    Generally, you may upgrade or replace all of the hardware components on your customer's computer and the end user may maintain the license for the original Microsoft® OEM operating system software, with the exception of an upgrade or replacement of the motherboard.

    An upgrade of the motherboard is considered to result in a "new personal computer" to which Microsoft® OEM operating system software cannot be transferred from another computer. If the motherboard is upgraded or replaced for reasons other than a defect, then a new computer has been created and the license of new operating system software is required.

    Note that while Software Assurance can be transferred from one PC to another, the bootable operating system may not be transferred from one PC to another, regardless of whether the PC has Software Assurance.

    If the motherboard is replaced because it is defective, you do NOT need to acquire a new operating system license for the PC.

    The reason for this licensing rule primarily relates to the end-user license agreement (EULA) and the support of the software covered by that EULA. The EULA is a set of usage rights granted to the end-user by the PC manufacturer and relates only to rights for that software as installed on that particular PC. The System Builder is required to support the software on that individual PC. Understanding that end users, over time, upgrade their PC with different components, Microsoft needed to have one base component "left standing" that would still define that original PC. Since the motherboard contains the CPU and is the "heart and soul" of the PC, when the motherboard is replaced (for reasons other than defect) a new PC is essentially created. The original System Builder, therefore, can not be expected to support this new PC that they in effect, did not manufacture.

  3. Old OEM SB packaging:

    Has a square COA available in 3 and 30 packs, sealed packs can be sold without hardware, individual copies must be sold with non-peripheral hardware or a PC.

    New OEM SB packaging:

    Has a round COA available in 1, 3, and 30 packs, sealed packs can be sold without hardware, individual copies must be sold with a PC.

  4. Microsoft encourages users to share their SP2 Update CDs however they prohibit installing WSUS on a public server.

    There are two types of hotfixes. GDR (General Distibution Release) hotfixes are tested and supported by MS and available through the download center and various update software (WU, OU, AU, SUS, MU, WSUS, and SMS). QFE (Quick Fix Engineering) hotfixes are provided as-is to fix specific problems and should only be installed on computers that need them, these are only available by request through MS support.

  5. Every Guest OS needs to be licenced. For Windows XP every vitual computer with a copy of Windows installed needs a licence. MS recently changed the licence terms for Windows 2003 and now you only need a Licence to use a virtual installation of Windows 2003. This change does not apply to Windows XP.

    Example: If you have 5 VMs with XP and 5 VMs with 2003 but you will only be running 1 of each at a time you will need 5 XP licences and 1 2003 licence. (This is in addition th the host computer's licence.)

  6. I am curious as to why you want to install from the dvd? It is much slower from the DVD than it is when it installs from the hard drive.

    Installing from a hard drive is faster than installing from a DVD but you have to copy the files from the DVD to your hard drive first, and that also takes time.

    The two reasons I have for installing apps from a CD is because I don't want my end users to have access to some of the source files and some of the computers I build don't have room for the entire source files on their hard drives.

    Why run a cleanup script when you can run clean from the beginning?

  7. How do the N editions remove WMP, do they have a differant txtsetup.sif or does the CD-Key determine if it will be an N edition? More importantly, how can I make my own N edition CD? (Don't say nLite, I want my OS to be recognized as an N edition)

  8. I wish I could use a DRAC card but there isn't one available for this unit. The 715N was Dell's first Windows based appliance and I guess thay didn't realize how important a local console is (the only ports on this unit is a serial port and 2 ethernet ports). The next model (725N) has PS/2, VGA, and bootable USB ports.

    The usual method for reinstalling is to download a floppy image with ghost and network support.

  9. I am interested installing Windows 2003 on a headless server (Dell PowerVault 715N) with no CD-ROM drive and want to know if RIS will work for me. The server redirects the BIOS output to a serial port until the OS or PXE image starts the boot process. Once the boot process starts the redirection gets turned off and I will have no I/O access to the server until Windows is installed. I have experiance making fully unattended CDs but never used RIS before.

  10. I think you want to use ProvideDefault. Unfortunately if a valid ProductKey is specified in winnt.sif ProvideDefault will skip that page

    ProvideDefault specifies that answers in the answer file are defaults. In this case, Setup displays these default answers to the user, who may change them if desired. This approach is useful in preinstallation scenarios where the OEM or administrator wants to give the person setting up the computer the option to change the predefined default answers (especially network options).

    DefaultHide specifies that answers in the answer file are defaults. Unlike the ProvideDefault value, Setup does not display the user interface to end users if all the answers relating to a particular wizard page are specified in the answer file. If only subsets of the answers on a page are specified, the page is displayed with the provided answers. The user can modify any of the answers on the displayed page. This approach is useful in deployment scenarios where an administrator may only want end users to provide the administrator password on the computer. This behavior is the default if unattended Setup mode is not specified.

  11. My question is with the ProductKey though. When I read the product key from a run of the mill Dell Dimension, the product key derived from the registry isn't what's on the side of the case... I've tested this on multiple machines and it seems like this applies to all Dell's. My best geuss is that dell uses a different product key than what is on the side of the case for one reason or another (maybe to avoid activation??).

    Since Dell computers don't have to be activated they use a factory key that cannot be activated on all their PCs. I'm not going to explain the rationale behind using the same key on all machines.

    Either way, would it be okay to use this ProductKey in the fresh install? I'm going to be using my own OEM cd, not the ones from Dell since each PC we get in is different and most of the time the customer lost the cd a long time ago. I'm thinking this would give me trouble when I go to activate, but I may be able to back up the WPA.DBL file?

    If you are using your own (hologrammed) CD you cannot use the Dell factory key because it cannot be activated. If you use the COA key you will have to activate over the phone. Dell reinstallation CDs are only limited to Dell computers, they are not model specific. You can make your own "Dell" CD by adding the Dell oembios files.

×
×
  • Create New...