Thursday, January 31, 2013

PATHS in return email

NOTES

SMTP id lm20mr8940610lab.42.1359663824660

Message-ID: <CAKiweZsJapgL1WsTJvWnBJB6xcVT4BUwoLqTLMXKJoanYwSqRg@mail.gmail.com



---------- Forwarded message ----------
From: Mail Delivery Subsystem
Date: Thursday, January 31, 2013
Subject: bookmarked 2 of 2
To: 50------gmail.com


Delivery to the following recipient failed permanently:

     50--------@gmail.com

Technical details of permanent failure:
The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at http://support.google.com/mail/bin/answer.py?answer=6596

----- Original message -----

Return-Path: <50----@gmail.com>
Received-SPF: pass (google.com: domain of 50-----@gmail.com designates 10.152.121.212 as permitted sender) client-ip=10.152.121.212
Authentication-Results: mr.google.com;
       spf=pass (google.com: domain of 504trackmyhack504@gmail.com designates 10.152.121.212 as permitted sender) smtp.mail=504trackmyhack504@gmail.com;
       dkim=pass header.i=@gmail.com
X-Received: from mr.google.com ([10.152.121.212])
        by 10.152.121.212 with SMTP id lm20mr8940610lab.42.1359663824666 (num_hops = 1);
        Thu, 31 Jan 2013 12:23:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to:cc
         :content-type;
        bh=2HjLGx+HygmqxpaeU/mGtJJ+DQw9CRusfhDXDzywNwo=;
        b=PX7w9FSa75CfZHZoCBRpxdxHUAzP1uBGzF4ueN4vomXTJvKluF3C/C7L1Al0ShnZnG
         zroQajta4+XsXdf9DmWKkHwCvfNsRGIc1cqu60QmFht4+KUu3PfUyhUTvFVKEPQX2D/i
         u0O5q/TrN7lfe6r6hK15nKcz8lo3wsAEGoiWEiLKpACyF1T6dh8bAXf3+Ww3OV6SsnUQ
         vBPuzORhiEw/PiiPHsH3SG0l5DgQxPQaBHTCRthe7WSDkDmIKT8qrtI7vVq8Ijm1fjJs
         4E+6zmjNWueJF2NxanFTp24yLGfnk+6LfAFwUC90LvY2Qe0BsyYMRHVIJdId4MHRQReR
         ONow==
MIME-Version: 1.0
X-Received: by 10.152.121.212 with SMTP id lm20mr8940610lab.42.1359663824660;
 Thu, 31 Jan 2013 12:23:44 -0800 (PST)
Received: by 10.152.135.38 with HTTP; Thu, 31 Jan 2013 12:23:44 -0800 (PST)
Date: Thu, 31 Jan 2013 12:23:44 -0800
Message-ID: <CAKiweZsJapgL1WsTJvWnBJB6xcVT4BUwoLqTLMXKJoanYwSqRg@mail.gmail.com>
Subject: bookmarked 2 of 2
From: blogger <504trackmyhack504@gmail.com>
To: Ruby Rhodes <rubyroadmail@gmail.com>
Cc: 504trackmyhack504.4812@gmail.com
Content-Type: multipart/alternative; boundary=f46d04374ee14868e604d49b6775

IP ADDRESS INFO

Host Name:bthmspsrvz3ts434-dmz.mycingular.netIP Address:166.147.88.48Country:United States Country code:US (USA)Region:City:Postal code:Calling code:+1Longitude:-97Latitude:38

Your IP address : 166.147.88.48Long IP address : 2794674224 Reverse DNS hostname : bthmspsrvz3ts434-dmz.mycingular.netYour Browser is: Mozilla/5.0 (Linux; U; Android 4.0.4; en-us; SAMSUNG-SGH-I717 Build/IMM76D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30Country Code = US USA United StatesRegion = City = Latitude = 38 : Longitude = -97Timezone = Friday 1st February, 2013You are the 1st visitor since 21 Juli 2011Java Enabled: falsePlatform: Linux armv7l


166.147.88.48

Your IP address : 166.147.88.48Long IP address : 2794674224 Reverse DNS hostname : bthmspsrvz3ts434-dmz.mycingular.netYour Browser is: Mozilla/5.0 (Linux; U; Android 4.0.4; en-us; SAMSUNG-SGH-I717 Build/IMM76D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30Country Code = US USA United StatesRegion = City = Latitude = 38 : Longitude = -97Timezone = Friday 1st February, 2013You are the 1st visitor since 21 Juli 2011Java Enabled: falsePlatform: Linux armv7lScreen-resolution: 1280 x 800Network Query Tool


http://www.imyip.it/


166.147.88.48 resolved to bthmspsrvz3ts434-dmz.mycingular.netDNS Query Results:; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5 <<>> any bthmspsrvz3ts434-dmz.mycingular.net;; global options: printcmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40992;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:;bthmspsrvz3ts434-dmz.mycingular.net. IN ANY;; ANSWER SECTION:bthmspsrvz3ts434-dmz.mycingular.net. 10800 IN A 166.147.88.48;; Query time: 210 msec;; SERVER: 192.168.1.90#53(192.168.1.90);; WHEN: Fri Feb 1 03:21:12 2013;; MSG SIZE rcvd: 69WWWhois Results:Connecting to whois.crsnic.net...NOT FOUND: No match for 166.147.88.48Whois Server Version 2.0Domain names in the .com and .net domains can now be registeredwith many different competing registrars. Go to http://www.internic.netfor detailed information.No match for "166.147.88.48".>>> Last update of whois database: Fri, 01 Feb 2013 02:20:37 UTC <<<NOTICE: The expiration date displayed in this record is the date the registrar's sponsorship of the domain name registration in the registry is currently set to expire. This date does not necessarily reflect the expiration date of the domain name registrant's agreement with the sponsoring registrar. Users may consult the sponsoring registrar's Whois database to view the registrar's reported date of expiration for this registration.TERMS OF USE: You are not authorized to access or query our Whois database through the use of electronic processes that are high-volume and automated except as reasonably necessary to register domain names or modify existing registrations; the Data in VeriSign Global Registry Services' ("VeriSign") Whois database is provided by VeriSign for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. VeriSign does not guarantee its accuracy. By submitting a Whois query, you agree to abide by the following terms of use: You agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to VeriSign (or its computer systems). The compilation, repackaging, dissemination or other use of this Data is expressly prohibited without the prior written consent of VeriSign. You agree not to use electronic processes that are automated and high-volume to access or query the Whois database except as reasonably necessary to register domain names or modify existing registrations. VeriSign reserves the right to restrict your access to the Whois database in its sole discretion to ensure operational stability. VeriSign may restrict or terminate your access to the Whois database for failure to abide by these terms of use. VeriSign reserves the right to modify these terms at any time. The Registry database contains ONLY .COM, .NET, .EDU domains andRegistrars.IP Whois Results:Connecting to whois.arin.net...## Query terms are ambiguous.  The query is assumed to be:#     "n 166.147.88.48"## Use "?" to get help.### The following results may also be obtained via:# http://whois.arin.net/rest/nets;q=166.147.88.48?showDetails=true&showARIN=false&ext=netref2#NetRange:       166.128.0.0 - 166.255.255.255CIDR:           166.128.0.0/9OriginAS:       NetName:        NETBLK-CDPD-BNetHandle:      NET-166-128-0-0-1Parent:         NET-166-0-0-0-0NetType:        Direct AssignmentRegDate:        1993-07-09Updated:        2005-01-07Ref:            http://whois.arin.net/rest/net/NET-166-128-0-0-1OrgName:        Service Provider CorporationOrgId:          SPC-10Address:        73 Old Dublin PikeAddress:        Suite 10 #315City:           DoylestownStateProv:      PAPostalCode:     18901-2491Country:        USRegDate:        1993-07-09Updated:        2009-11-16Ref:            http://whois.arin.net/rest/org/SPC-10OrgNOCHandle: WDSPC-ARINOrgNOCName:   WDSPCo HelpdeskOrgNOCPhone:  +1-215-489-7599 OrgNOCEmail:  ipabuse@wdspco.orgOrgNOCRef:    http://whois.arin.net/rest/poc/WDSPC-ARINOrgAbuseHandle: WDSPC-ARINOrgAbuseName:   WDSPCo HelpdeskOrgAbusePhone:  +1-215-489-7599 OrgAbuseEmail:  ipabuse@wdspco.orgOrgAbuseRef:    http://whois.arin.net/rest/poc/WDSPC-ARINOrgTechHandle: WDSPC-ARINOrgTechName:   WDSPCo HelpdeskOrgTechPhone:  +1-215-489-7599 OrgTechEmail:  ipabuse@wdspco.orgOrgTechRef:    http://whois.arin.net/rest/poc/WDSPC-ARINRTechHandle: WDSPC-ARINRTechName:   WDSPCo HelpdeskRTechPhone:  +1-215-489-7599 RTechEmail:  ipabuse@wdspco.orgRTechRef:    http://whois.arin.net/rest/poc/WDSPC-ARIN## ARIN WHOIS data and services are subject to the Terms of Use# available at: https://www.arin.net/whois_tou.html#Checking Port 80...Port 80 does not appear to be open.Traceroute Results:Traceroute failed. Host may not be active.

http://www.myip.it/SubnetCalc.php


  IP Address:  166.147.88.48  Host Name:  bthmspsrvz3ts434-dmz.mycingular.net  Host Location:  Denver, Colorado, United States   Spam Blacklisted: Unknown - temporary  Operating System:  lin  Current Time:  Thursday, January 31, 2013 08:30:10 PM CST

|||||||
http://www.findmyip.org/

http://www.topwebhosts.org/tools/index.php


Location not accurate? Try: Update IP Location

IP Information: 166.147.88.28

ISP:AT&T WirelessOrganization:AT&T WirelessConnection:Dial-upServices:Suspected Network Sharing DeviceCity:LynnwoodRegion:WashingtonCountry:United States 


General IP Information

IP:166.147.88.28Decimal:2794674204Hostname:bthmspsrvz3ts214-dmz.mycingular.netISP:AT&T WirelessOrganization:AT&T WirelessServices:Confirmed proxy serverType:Wireless BroadbandAssignment:Static IPBlacklist:

Geolocation Information

Country:United States State/Region:WashingtonCity:LynnwoodLatitude:47.8209  (47° 49′ 15.24″ N)Longitude:-122.3151  (122° 18′ 54.36″ W)Area Code:425Location not accurate? Update your location

Geolocation Map


CityPostal CodeLatitude38Longitude-97Area Code0

Traceroute

Tracing route to 166.147.88.48HopTimeHostIPLocation10.69510.0.0.110.0.0.1, ,20.823140.239.191.1140.239.191.1Los Angeles, CA, United States38.13ip65-47-242-9.z242-47-65.customer.algx.net65.47.242.9Los Angeles, CA, United States47.366207.88.81.193.ptr.us.xo.net207.88.81.193, , United States59.807ae1d0.mcr1.la-ca.us.xo.net216.156.1.57, , United States69.786vb1400.rar3.la-ca.us.xo.net216.156.0.113, , United States710.115207.88.14.218.ptr.us.xo.net207.88.14.218, , United States834.858205.158.79.242.ptr.us.xo.net205.158.79.242, , United States946.004cr2.la2ca.ip.att.net12.123.30.190, , United States1048.104cr2.sffca.ip.att.net12.122.31.134, , United States1144.438cr1.st6wa.ip.att.net12.122.31.193, , United States1241.06912.83.180.112.83.180.1, , United States1340.52812.249.2.2612.249.2.26Middletown, NJ, United States21N/Abthmspsrvz3ts434-dmz.mycingular.net166.147.88.48, ,

Geo-Location Map






||||||












PE Boot PROTECTION Machine Policies (Windows)


http://msdn.microsoft.com/en-us/library/windows/desktop/aa372395(v=vs.85).aspx

Machine Policies (Windows)

User Policies (Windows)

The following user policies can be configured underHKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\InstallerValue nameValue data typesDescriptionAlwaysInstallElevatedREG_DWORDIf this value is set to "1" and the corresponding computer value is also set, the installer always installs with elevated privileges.Otherwise, the installer uses elevated privileges to install managed applications and uses the current user's privilege level for nonmanaged applications.DisableMediaREG_DWORDIf the DisableMedia policy is set to "1", users and administrators running a maintenance installation of one product are prevented from using the Browse Dialog to browse media sources, such as CD-ROM, for the sources of other installable products. Browsing for other products is prevented regardless of whether the installation is with elevated privileges. It is still possible for the user to reinstall the product from media if the user has a correctly labeled media source.DisableRollbackREG_DWORDIf this value is set to "1", the installer will not store rollback files during installation, disabling installation rollback. By default, rollback is enabled. Administrators are advised to not use this policy unless it is absolutely essential.SearchOrderREG_SZOrder in which the installer searches the three different types of sources:"n"– network"m"– media (CD-ROM or DVD)"u"– URL (Uniform Resource Locator)For example, a value of "nmu" instructs the installer to search network sources first, media sources second, and URL sources last. Leaving out a letter removes the corresponding volume type from the search. Default order in absence of this value is network first, then media followed by URL.TransformsAtSource policyREG_DWORDIf this value exists and is set to "1"; the installer searches for transform files in the root of any network sources in the sourcelist for the product. By default, transforms are stored in the Application Data folder of a user's profile.   


Machine Policies (Windows)


The following machine policies can be configured under:HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\InstallerPolicyValue data typeDescriptionAlwaysInstallElevatedREG_DWORDIf this policy value is set to 1 and the corresponding user value is also set, the installer always installs with elevated privileges.Otherwise, the installer uses elevated privileges to install managed applications and uses the current user's privilege level for unmanaged applications.AllowLockdownBrowseREG_DWORDIf this policy value is set to 1, non-administrative users can browse for new sources while running an installation at elevated privileges. The default is that only administrators can browse for sources during an elevated installation. Setting this policy also enables non-administrative users to run programs at LocalSystem privileges during an elevated installation.AllowLockdownMediaREG_DWORDIf this policy value is set to 1, non-administrative users can use media sources, such as a CD-ROM, while running an installation at elevated privileges. The default is that only administrators can use media sources during an elevated installation. Setting this policy also enables non-administrative users to run programs at LocalSystem privileges during an elevated installation.AllowLockdownPatchREG_DWORDIf this per-machine system policy value is not set, only administrators can patch existing products that were installed at elevated privileges. If this policy value is set to 1, non-administrative users can, in some cases, apply patches to products while running an installation using elevated privileges. With the policy set, the patch can install minor upgrades while running an installation using elevated privileges; the patch cannot install major upgrades. Setting this policy also enables non-administrative users to run programs at LocalSystem privileges during an elevated installation.DebugREG_DWORDIf this policy value exists and is set to 1, the installer writes common debugging messages to the debugger using the OutputDebugString function. If this value exists and is set to 2, the installer writes all valid debugging messages to the debugger using the OutputDebugString function.This policy is for debugging purposes only and may not be supported in future versions of Windows Installer.DisableAutomaticApplicationShutdownREG_DWORDIf this policy value exists and is set to 1, Windows Installer does not interact with Restart Manager but will use theFilesInUse Dialog functionality.Windows Installer 3.1 and earlier:  Not supported.DisableBrowseREG_DWORDIf this policy value exists and is set to 1, users are prevented from browsing to locate installer sources. The Use feature from combo box for direct input is locked and the Browse button is disabled. For more information about source browsing, see Source Resiliency.DisableFlyWeightPatchingREG_DWORDIf this per-machine system policy value is set to 1, allPatch Optimization options are turned off during the installation.Windows Installer 2.0:  Not supported.DisableLUAPatchingREG_DWORDIf this per-machine system policy value is set to 1, the installer prevents non-administrators from using least-privileged account (LUA) patching to any application installed on the computer. When this value is not set or 0, non-administrators can apply LUA patches to LUA-enabled application.DisableMSIREG_DWORDIf this policy value is set to 0, is absent, or any number other than 1 or 2, the effect on the Windows Installer depends on the operating system. On Windows Server 2003, Windows Installer is enabled for managed applications and disabled for unmanaged application installs. On Windows XP the Windows Installer is enabled for all applications.If this policy value is set to 0, Windows Installer is enabled for all applications. All install operations are allowed.If this policy value is set to 1, Windows Installer is disabled for unmanaged applications but is still enabled for managed applications. Non-elevated per-user installations are blocked. Per-user elevated and per-machine installs are allowed.If this policy value is set to 2, Windows Installer is always disabled for all applications. No installs are allowed including repairs, reinstalls, or on-demand installations.DisablePatchREG_DWORDIf this policy value is set to 1 the installer does not apply patches. This policy can be used to provide security in environments where patching must be restricted.DisablePatchUninstallREG_DWORDIf this policy value is set to 1, patches cannot be removed from the computer by a user or an administrator. The Windows Installer can still remove patches that are no longer applicable to a product.Windows Installer 2.0:  Not supported.DisableRollbackREG_DWORDIf this policy value is set to 1, the installer does not store rollback files during installation, disabling installation rollback. By default, rollback is enabled. Administrators are advised not to use this policy unless it is absolutely essential.DisableSharedComponentREG_DWORDIf this per-machine system policy is set to 1, no package on the system gets the shared component functionality enabled by the msidbComponentAttributesSharedattribute in the Component table.DisableUserInstallsREG_DWORDIf this policy value is not set, the installer searches the registry for products in the following order: managed products that are registered as per-user, unmanaged products that are registered as per-user, and finally products that are registered as per-machine.If this policy value is set to 1, the installer ignores all products that are registered as per-user and only searches for products that are registered as per-machine. An attempt to perform a per-user installation causes the installer to display an error message and stops the installation.EnforceUpgradeComponentRulesREG_DWORDSet this policy value to 1 to apply upgrade component rules during small updates and minor upgrades of all products on the computer.Windows Installer 2.0:  Not supported.EnableAdminTSRemoteREG_DWORDSetting this policy enables administrators to perform installations from a client session of a server running the Terminal Server role service.EnableUserControlREG_DWORDIf this policy value is set to 1, then the installer can pass allpublic properties to the server side during a managed installation using elevated privileges. Setting this policy has the same effect as setting the EnableUserControlproperty.LimitSystemRestoreCheckpointingREG_DWORDThis policy turns off the creation of checkpoints by Windows Installer.If the policy value is set to 0 or absent, Windows Installer does normal checkpointing for install or uninstall.If the policy value is set to 1, Windows Installer creates no checkpoints.LoggingREG_SZThis policy value is used only if logging has not been enabled by the "/L" command-line option or MsiEnableLog. If a policy is set in this case, a log file is created in the temp directory with the random name: MSI*.LOG. Specify the logging mode by setting the policy value to a string of characters. Use the same characters to specify logging mode policy as used by the "/L" command-line option. For more information, seeCommand Line Options. Note that you cannot use "+" and "*" for the policy.MaxPatchCacheSizeREG_DWORDIf this policy value is set to a value greater than 0, Windows Installer saves old versions of patched files in a cache. Set the value to the maximum percentage of disk space that can be used for the file cache. For example, a value of 15 and sets the maximum to 15%. Set to 0 to save no files. When this policy is not set, the default is 10%.MsiDisableEmbeddedUIREG_DWORDTo disable embedded UI handlers on the computer, set this policy value to 1.Windows Installer 4.0 and earlier:  Not supported.SafeForScriptingREG_DWORDIf this policy value is set to 1, users are not prompted when scripts use installer automation within a Web page. This may be useful for Web-based tools but can allow silent installations of applications without user knowledge or consent.TransformsSecure policyREG_DWORDSetting the TransformsSecure policy value to 1 informs the installer that transforms are to be cached locally on the user's computer in a location where the user does not have write access.DisableLoggingFromPackageREG_DWORDSet this policy value to 1 to disable the logging specified for the package by the MsiLogging property for all users of the computer.Windows Installer 3.1 and earlier:  Not supported.WinHttpAutoLogonLevelREG_SZThe automatic logon (auto-logon) policy determines when it is acceptable to include the default credentials in a request to the server.Windows 8 and Windows Server 2012:  This policy requires Windows Installer running on the Windows 8 or Windows Server 2012 and is unavailable on all earlier versions of Windows. 

http://msdn.microsoft.com/en-us/library/windows/desktop/aa372868(v=vs.85).aspx



Windows Installer adheres to Windows Resource Protection (WRP) when installing essential system files, folders, and registry information in Windows Server 2008 and later and Windows Vista and later.WRP in Windows Server 2008 and Windows Vista replaces Windows File Protection (WFP) in Windows Server 2003, Windows XP, and Windows 2000. Windows Installer developers should note the following changes in how the installer handles protected resources in Windows Server 2008 and later and Windows Vista and later:When running on Windows Server 2008 and later or Windows Vista and later, the Windows Installer skips the installation of any file that is protected by WRP, the installer enters a warning in the log file, and continues with the remainder of the installation without an error. In Windows Server 2003, Windows XP, and Windows 2000, when the Windows Installer encountered a WFP-protected file, the installer would request that WFP install the file.WRP on Windows Server 2008 and later or Windows Vista and later can protect registry keys in addition to files. If the Windows Installer encounters a WRP-protected registry key, the installer skips the installation of that registry key, the installer enters a warning in the log file, and continues with the remainder of the installation without an error.Note that if a Windows Installer component contains a file or registry key that is protected by WRP, this resource must be used as the KeyPath for the component. In this case, Windows Installer does not install, update, or remove the component. You should not include any protected resources in an installation package. Instead, you should use the supported resource replacement mechanisms for Windows Resource Protection.For more information about WRP, see Windows Resource Protection and information that is provided on Microsoft Technet.

WFP for Windows Server 2003 and Windows XP/2000

Windows Installer adheres to Windows File Protection (WFP) when installing essential system files on Windows Server 2003, Windows XP and Windows 2000. If a protected system file is modified by an unattended installation of an application, WFP restores the file to the verified file version.Windows Installer never attempts to install or replace a protected file. When the InstallFiles action or any other action scheduled before InstallFiles attempts to install a file protected on Windows Server 2003, Windows XP or Windows 2000, the installer calls WFP with a request to install or replace the protected file. The installer requests the file installation from WFP immediately after executing the InstallFiles action. WFP installs or replaces the file on the user's system with a cached version of the protected file. Note that this does not guarantee that the version of the file installed from the cache is the version required by the application. After WFP has installed the file, the installer determines whether this version matches the version in the package. If the file version in the package is greater than the installed version, the installer informs the user that it cannot update the system and that an update of the operating system may be required for the application.If any action sequenced after InstallFiles attempts to install or replace a protected file not already installed on the system, the installer cannot call WFP to install the file. In this case, the installer informs the user that it cannot update the system and that an update of the operating system may be required for the application.The installer also checks with WFP when removing files and never attempts to remove protected system files.

Component Key Files Protected by WFP

Note that if a Windows Installer component contains a WFP file, this file must be specified as the key path for the component.When the installer attempts to install a component's key file on Windows Server 2003, Windows XP or Windows 2000, it first calls WFP to determine if the key file is protected. When the key file of a component is protected by WFP, and that key file is already installed, the installer updates the component only if the version of the key file in the package is greater than the installed version. If the installation package specifies that a component be installed, and the key file of the component is not currently installed, then regardless of whether the key file is protected the installer installs the component. Once any component having a key file protected by WFP is installed, it is permanently installed, and the installer never removes or replaces the component.

Installation of Assemblies by WFP

WFP for assemblies differs from WFP for system files.WFP protects Windows Server 2003, Windows XP and Windows 2000 system files by detecting attempts to replace protected system files. This protection is triggered after WFP receives a directory change notification for a file in a protected directory. When WFP receives this notification, it determines which file has changed. If the file is protected, WFP looks up the file signature in a static catalog file to determine if the new file is the correct version. If the file version is not correct, the system replaces the file with the correct version from either the cache or distribution media.In contrast, WFP of assemblies is dynamic. WFP is extended to files as they are added to the shared side-by-side assembly cache. If an assembly becomes corrupted, WFP will request that the installer replace the file. Windows Installer may or may not be able to replace the file depending on whether the source package is accessible. If the source package is inaccessible, WFP will put up a dialog box stating that it is unable to restore the file.Note that unmanaged shared side-by-side assemblies, installed in %windir%\winsxs, are protected by WFP. Unmanaged private assemblies, installed in the application directory, are not protected by WFP. Managed global assemblies installed in the application directory or %windir%\assembly\gac are not protected by WFP.

Related topics

Windows Resource Protection


out of 13 rated this helpful - Rate this topicReplacement of protected resources is supported through the following mechanisms.Permission for full access to modify WRP-protected resources on Windows Vista and Windows Server 2008 is restricted to TrustedInstaller with the Windows Modules Installer service using the following mechanisms:Windows Service Packs installed by TrustedInstaller.Hotfixes installed by TrustedInstaller.Operating system upgrades installed by TrustedInstaller.Windows Update installed by TrustedInstaller.Applications and installers attempting to replace a WRP-protected resource by means other than these specified methods are denied access to change the resource and generate an access denied error message.For well-known installers attempting to replace WRP-protected resources, the access denied error and error message may be suppressed. In this case, the operation returns successfully, the error and error message are suppressed, but no changes are applied to the WRP-protected resource. The error may be suppressed for a well-known installer only when all of the following criteria are satisfied:This is a legacy application. The application does not include a manifest with a requestedExecutionlevel that identifies the application as designed for Windows Vista or Windows Server 2008.The access denied error is caused only by the attempt to modify a WRP-protected resource.An Administrator is installing the application.For information about using the Windows Installer with WRP, see Using Windows Installer and Windows Resource Protection in the Windows Installer SDK.Windows Server 2003 and Windows XP:  Replacement of WFP-protected system files is supported only through the following mechanisms:Windows Service Pack installation using Update.exeHotfixes installed using Hotfix.exeOperating system upgrades using Winnt32.exeWindows UpdateReplacing protected files by means other than these specified methods results in the original files being restored by WFP.  Send comments about this topic to Microsoft


9 out of 17 rated this helpful - Rate this topicPermission for full access to modify WRP-protected resources is restricted to TrustedInstaller. WRP-protected resources can be changed only using the Supported Resource Replacement Mechanisms with the Windows Modules Installer service.WRP protects files with the following extensions that are installed by Windows Server 2008 or Windows Vista: .dll, .exe, .ocx, and .sys.WRP protects critical files that are installed by Windows Server 2008 or Windows Vista with the following extensions: .acm, .ade, .adp, .app, .asa, .asp, .aspx, .ax, .bas, .bat, .bin, .cer, .chm, .clb, .cmd, .cnt, .cnv, .com, .cpl, .cpx, .crt, .csh, .dll, .drv, .dtd, .exe, .fxp, .grp, .h1s, .hlp, .hta, .ime, .inf, .ins, .isp, .its, .js, .jse, .ksh, .lnk, .mad, .maf, .mag, .mam, .man, .maq, .mar, .mas, .mat, .mau, .mav, .maw, .mda, .mdb, .mde, .mdt, .mdw, .mdz, .msc, .msi, .msp, .mst, .mui, .nls, .ocx, .ops, .pal, .pcd, .pif, .prf, .prg, .pst, .reg, .scf, .scr, .sct, .shb, .shs, .sys, .tlb, .tsp, .url, .vb, .vbe, .vbs, .vsmacros, .vss, .vst, .vsw, .ws, .wsc, .wsf, .wsh, .xsd, and .xsl.WRP protects critical folders. A folder containing only WRP-protected files may be locked so that only the Windows trusted installer is able to create files or subfolders in the folder. A folder may be partially locked to enable Administrators to create files and subfolders in the folder.WRP protects essential registry keys installed by Windows Server 2008 and Windows Vista. If a key is protected by WRP, all its subkeys and values can be protected.WRP copies files that are needed to restart Windows in the cache directory located at %Windir%\winsxs\Backup. Critical files that are not needed to restart Windows are not copied to the cache directory. The size of the cache directory and the list of files copied to cache cannot be modified.Windows Server 2003 and Windows XP:  Windows File Protection (WFP) preceded WRP.WFP protects files that are installed by Windows with the following extensions: .dll, .exe, .ocx, and .sys. In addition, the TrueType fonts Micross.ttf, Tahoma.ttf, and Tahomabd.ttf are also protected.At the end of the Windows installation, WFP runs a scan of all protected files to ensure they have not been modified by applications installed through unattended installation. WFP also copies verified versions of these system files to the cache directory. When an application attempts to replace a protected file, WFP can restore the original file from the cache directory.The default value is %systemroot%\system32\dllcache. To specify a different location for the cache, create the following registry value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SFCDllCacheDirThis must be a local path. Using a network path creates a single shared network source for cache files, provided all clients using the share are running the same service packs and hotfixes.The default size of the cache is unlimited. To change the size of the cache, use the following registry setting: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SFCQuotaIf the value is SFC_QUOTA_ALL_FILES, all system files will be cached in the cache directory.Due to disk space considerations, it may not be desirable to maintain cached versions of all system files in the cache directory. Depending on the size of the cache, WFP will store verified file versions in the cache directory on the system hard drive. WFP will add files to the cache until the size of the cache directory reaches the specified limit.When an application attempts to replace a protected file that is not in the cache, WFP attempts to restore the original file from the installation source, prompting the user if necessary.  Send comments about this topic to Microsoft

FP registry values are not supported as of Windows Vista.]WFP uses several registry values for customization settings. The WFP registry values are located in the following registry key:HKEY_LOCAL_MACHINE    SOFTWARE       Microsoft          Windows NT             CurrentVersion                WinlogonThe following are the WFP registry values.SFCDllCacheDirLocation of the cache. This must be a local path. The default value is %systemroot%\system32\dllcache.SFCQuotaQuota options. This registry value can be one of the following values.ValueMeaningSFC_QUOTA_ALL_FILESSize of the DLL cache is unlimited. This is the default.Other valuesSize of the DLL cache, in files. SFCScanScan options. This registry value can be one of the following values.ValueMeaningSFC_SCAN_NORMALDo not scan protected files at boot. This is the default.SFC_SCAN_ALWAYSScan protected files at every boot.SFC_SCAN_ONCEScan protected files at the next boot.
http://support.microsoft.com/kb/832017

Wednesday, January 30, 2013

Ro Domain

http://msdn.microsoft.com/en-us/library/bb756900.aspx


Application Compatibility: Microsoft Graphical Identification and Authentication (GINA)

2 out of 4 rated this helpful - Rate this topicMicrosoft Graphical Identification and Authentication (GINA)

Feature Impact

High (frequency: low)

Brief Description

Prior to Windows Vista® and Windows Server® 2008, for logons to a third-party server or with a third-party device, ISVs had to replace the Graphical Identification and Authentication (GINA) dynamic-link library in Windows XP®. Such applications also had to replace the existing UI and implement smart-card and remote-desktop features on Windows XP.Note:If an application did not function this way in Windows XP, this information does not apply.Windows Vista and Windows Server 2008 introduce a new authentication model where LogonUI and WinLogon communicate directly with each other. This model provides a simplicity, scalability, and flexibility that did not exist with GINA. Unlike with the GINA module, ISVs no longer need to replace the UI for the logon screen, thus relieving the ISV of the burden of re-authoring the user interface for the user. An ISV can author a credential provider, which is a module that plugs into the LogonUI, to describe the UI and to gather the credential and pass it on to WinLogon. Credential providers are completely transparent to WinLogon.Credential providers are also additive, meaning that users can install multiple credential providers and pick the one that they want to use. Credential providers can be user-selected, event-driven, or both. Multiple credential providers can coexist on Windows Vista and Windows Server 2008 and are not only for third parties. In fact, Windows will ship two credential providers in the box: a credential provider for user name and password and a credential provider for smart card.Additionally, credential providers can be reused within CredUI. That is, the same object that describes and collects credential information on LogonUI can be used to gather the very same credentials in CredUI scenarios.The GINA functionality from Windows XP and Windows Server 2003 has been deprecated and removed from Windows Vista and Windows Server 2008. The GINA modules of applications will not function and must be re-authored using the new authentication model for Windows Vista and Windows Server 2008.

Manifestation

The user will not be able to successfully install custom logon applications.The user will not be able to log on using custom logon applications (using the Windows XP technology) in Windows Vista and Windows Server 2008. These applications might include biometric devices, custom logon UI, or virtual private network (VPN) solutions for remote users with custom logon UI.

Remedies

Leverage new capability:The applications or components that use the GINA technology must be re-authored to use the new logon authentication model for Windows Vista and Windows Server 2008.

Links to Other Resources

For all credential provider information and questions, send e-mail to the Shell Credential Provider alias: credprov@microsoft.com.See Also



Application Compatibility: Read Only Domain Controllers (RODC)

This topic has not yet been rated - Rate this topicRead-Only Domain Controllers (RODC)

Feature Impact

Moderate

Brief Description

A Read-Only Domain Controller (RODC) is a new type of domain controller under the Windows Server 2008 operating system. With an RODC, organizations can easily deploy a domain controller in locations where physical security cannot be guaranteed. An RODC hosts a read-only replica of the database in Active Directory® Domain Services (AD DS) for a given domain.Before the release of Windows Server 2008, if users had to authenticate with a domain controller over a wide area network (WAN), there was no real alternative. In many cases, this solution was not efficient. Branch offices often cannot provide adequate physical security that is required for a writable domain controller. Furthermore, branch offices often have poor network bandwidth when connected to a hub site. This limitation can increase the amount of time required to log on; it can also hamper access to network resources.Beginning with Windows Server 2008, an organization can deploy an RODC to address these problems. As a result, users in this situation can benefit from:Improved security.Faster logon times.More efficient access to resources on the network.

Manifestation

Any application that writes to the Active Directory is potentially impacted by RODCs and might see compatibility issues involving failed writes or failed reads of newly written data.

Remedies

Applications that write data might locate a domain controller using methods that do not differentiate between writable and read-only domain controllers.There are two methods that applications typically use to request the nearest domain controller:Serverless binding, as recommended in Binding to Active Directory Domain ServicesDomain controller Locator callsIn Windows Server 2008, a domain controller Locator call can return any domain controller, including a domain controller running Windows 2000 Server or Windows Server 2003 or a writable or read-only domain controller running Windows Server 2008.Problems can occur if an application needs to write to directory objects and it gets an RODC from calling a serverless bind. In that case, the write operations are referred to a writable domain controller running Windows Server 2008 at the hub site. Depending on the WAN connection to the hub site at that time, the application can fail to connect to the hub and can report errors. The application must also correctly handle these referrals. Even if the write operation succeeds, any subsequent reading of the data that was just written might fail because of inherent latency that is required to replicate this data back to the RODC.Applications that must run on a domain controller should be aware of RODCs. These applications must determine if the domain controller is writable or if it is an RODC. Checking the registry or using OSVERSIONINFOEX, as discussed in OSVERSIONINFOEX Structure, does not distinguish an RODC from a writable domain controller. An RODC still advertises itself as a domain controller.To making this determination, check the supportedCapabilities attribute on the rootDSE class. For more information, see Serverless Binding and RootDSE. The presence of object identifier value 1.2.840.113556.1.4.1920 indicates that the specified domain controller is an RODC.You can also use the DsRoleGetPrimaryDomainInformation function to determine if the domain controller is an RODC. A new flag has been added to the DSROLE_PRIMARY_DOMAIN_INFO_BASIC structure.

Links to Other Resources

Application Compatibility with RODCsThe Future of Active Directory (February 22, 2006) chatThe Future of Windows: Directory Services in Windows Server 2008See Also









In my mobile browser address

http://www.wolframalpha.com/samsung/?i=%3Cmath+xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F1998%2FMath%2FMathML%22%3E%0A++%3Cmstyle+displaystyle%3D%22true%22%3E%0A++++%3Cmn%3E+1.+%3C%2Fmn%3E%0A++%3C%2Fmstyle%3E%0A%3C%2Fmath%3E&device=SAMSUNG-SGH-I717&mag=2&width=800&inputsource=equation&density=1










-









-




HARD DRIVE

ow to list physical disks?

c windows winapi hard-driveHow to list physical disks in windows? In order to obtain a list of "\.\PhysicalDrive0" available.improve this questionedited Nov 29 '08 at 17:56asked Nov 29 '08 at 17:18CiNN2,551●2●19●349 Answersorder by                      active                     oldest                     votes                 vote up18vote downwmic is a very complete toolwmic diskdrive listprovide a (too much) detailed list, for instancefor less infowmic diskdrive list brief improve this answeredited Jan 17 '12 at 16:07Community♦ answered Nov 29 '08 at 17:24VonC274k●51●512●657-1 Does not answer the question, which is asking for how to do it in C. – unixman83 Feb 16 '12 at 13:26+1 Does not answer the question, but it is a very useful piece of information :-) – Grodriguez Jul 27 '12 at 7:531 you could do a system("wmic diskdrive list"); in C – Sebastian Godelet Nov 21 '12 at 13:28vote up7vote downI've modified an open-source program called "dskwipe" in order to pull this disk information out of it. Dskwipe is written in C, and you can pull this function out of it. The binary and source are available here: dskwipe 0.3 has been releasedThe returned information will look something like this:Device Name Size Type Partition Type ------------------------------ --------- --------- -------------------- \\.\PhysicalDrive0 40.0 GB Fixed \\.\PhysicalDrive1 80.0 GB Fixed \Device\Harddisk0\Partition0 40.0 GB Fixed \Device\Harddisk0\Partition1 40.0 GB Fixed NTFS \Device\Harddisk1\Partition0 80.0 GB Fixed \Device\Harddisk1\Partition1 80.0 GB Fixed NTFS \\.\C: 80.0 GB Fixed NTFS \\.\D: 2.1 GB Fixed FAT32 \\.\E: 40.0 GB Fixed NTFSimprove this answeranswered Dec 8 '08 at 17:55Mick6,389●1●24●631 i thought it was it, but it force brute search for the drives..isn't there an api that will just report back the devices ? – CiNN Dec 9 '08 at 23:031 Yes. SetupApi in Win32, function names start with SetupDi – Warren P Dec 16 '11 at 20:06vote up5vote downFrom your own code, use GetLogicalDrives() first to get all of the drives mapped in the system, and then GetDriveType() to find out which sort of drive each one is.improve this answeredited Nov 29 '08 at 17:31answered Nov 29 '08 at 17:26Alnitak89.1k●10●119●1901 It is not correct because logical drives don't correspond to physical ones. – Sergius Jan 18 '12 at 11:48vote up5vote downGetLogicalDrives() enumerates all mounted disk partitions, not physical drives.You can enumerate the drive letters with (or without) GetLogicalDrives, then call QueryDosDevice() to find out which physical drive the letter is mapped to.Alternatively, you can decode the information in the registry at HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices. The binary data encodings there are not obvious, however. If you have a copy of Russinovich and Solomon's book Microsoft Windows Internals, this registry hive is discussed in Chapter 10.improve this answeranswered Nov 29 '08 at 18:11Die in Sente3,315●10●24can you provide example code? – Chibueze Opata Mar 15 '12 at 14:35QueryDosDevice retuens partition, not the disk itself. Single disk is split to C: and D:, Win7 x64. So: c => "\Device\HarddiskVolume2"; d => "\Device\HarddiskVolume3'" – Arioch 'The Jul 25 '12 at 12:47vote up2vote downThe only sure shot way to do this is to call CreateFile() on all \\.\Physicaldiskxwhere x is from 0 to 15 (16 is maximum number of disks allowed). Check the returned handle value. If invalid check GetLastError() for ERROR_FILE_NOT_FOUND. If it returns anything else then the disk exists but you cannot access it for some reason.improve this answeredited Apr 19 '12 at 16:23Charles Menguy answered Apr 19 '12 at 12:26anni60●5vote up2vote downOne way to do it:Enumerate logical drives using GetLogicalDrivesFor each logical drive, open a file named "\\.\X:" (without the quotes) where X is the logical drive letter.Call DeviceIoControl passing the handle to the file opened in the previous step, and the dwIoControlCode parameter set to IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS:HANDLE hHandle; VOLUME_DISK_EXTENTS diskExtents; DWORD dwSize; [...] iRes = DeviceIoControl( hHandle, IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS, NULL, 0, (LPVOID) &diskExtents, (DWORD) sizeof(diskExtents), (LPDWORD) &dwSize, NULL);This returns information of the physical location of a logical volume, as a VOLUME_DISK_EXTENTS structure.In the simple case where the volume resides on a single physical drive, the physical drive number is available in diskExtents.Extents[0].DiskNumberimprove this answeranswered Jul 27 '12 at 8:09Grodriguez6,474●16●341 +1 Certainly a more accurate answer than mine ;) – VonC Jul 27 '12 at 8:14vote up1vote downI just ran across this in my RSS Reader today. I've got a cleaner solution for you. This example is in Delphi, but can very easily be converted to C/C++ (It's all Win32).Query all value names from the following registry location:HKLM\SYSTEM\MountedDevicesOne by one, pass them into the following function and you will be returned the device name. Pretty clean and simple! I found this code on a blog here.function VolumeNameToDeviceName(const VolName: String): String; var s: String; TargetPath: Array[0..MAX_PATH] of WideChar; bSucceeded: Boolean; begin Result := "; // VolumeName has a format like this: \\?\Volume{c4ee0265-bada-11dd-9cd5-806e6f6e6963}\ // We need to strip this to Volume{c4ee0265-bada-11dd-9cd5-806e6f6e6963} s := Copy(VolName, 5, Length(VolName) - 5); bSucceeded := QueryDosDeviceW(PWideChar(WideString(s)), TargetPath, MAX_PATH) <> 0; if bSucceeded then begin Result := TargetPath; end else begin // raise exception end; end;improve this answeranswered Dec 10 '08 at 16:31Mick6,389●1●24●631 i want to have the physical name so that i could play with unallocated space, so my guess it that this unallocated space wouldn't have a mounted volume guid... – CiNN Dec 12 '08 at 8:451 'Fraid this isn't what we're looking for, and is similar to @Alnitak's answer. – Matt Joiner Oct 28 '10 at 10:301 You're supposed to use SetupApi in windows xp and later, and no longer use the registry, which was the way to do it in Win98, but not any more. – Warren P Dec 16 '11 at 20:07vote up1vote downI think this is a very good sample for your question, a little late but... its validimprove this answeranswered Feb 6 '10 at 18:10Eugenio Miró741●8●151 As far as I can tell (and I've tested the code you linked too), volumes don't relate to partitions in a 1 to many fashion, and don't give the access the OP is asking for. – Matt Joiner Oct 28 '10 at 10:34This answer doesn't deserve -1. It is no worse than other answers on this page and it's in C. – unixman83 Feb 16 '12 at 13:03vote up0vote downMake a list of all letters in the US English Alphabet, skipping a & b. "CDEFGHIJKLMNOPQRSTUVWXYZ". Open each of those drives with CreateFile e.g. CreateFile("\\.\C:"). If it does not return INVALID_HANDLE_VALUE then you got a 'good' drive. Next take that handle and run it through DeviceIoControl to get the Disk #.See my related answer for more details.improve this answer

CONTACT,AT MICROSOFT.RE.CA. CERTS!!

Links to Other Resources

For all credential provider information and questions, send e-mail to the Shell Credential Provider alias: credprov@microsoft.com.

http://msdn.microsoft.com/en-us/library/bb756900.aspx


Application Compatibility: Microsoft Graphical Identification and Authentication (GINA)

2 out of 4 rated this helpful - Rate this topicMicrosoft Graphical Identification and Authentication (GINA)

Feature Impact

High (frequency: low)

Brief Description

Prior to Windows Vista® and Windows Server® 2008, for logons to a third-party server or with a third-party device, ISVs had to replace the Graphical Identification and Authentication (GINA) dynamic-link library in Windows XP®. Such applications also had to replace the existing UI and implement smart-card and remote-desktop features on Windows XP.Note:If an application did not function this way in Windows XP, this information does not apply.Windows Vista and Windows Server 2008 introduce a new authentication model where LogonUI and WinLogon communicate directly with each other. This model provides a simplicity, scalability, and flexibility that did not exist with GINA. Unlike with the GINA module, ISVs no longer need to replace the UI for the logon screen, thus relieving the ISV of the burden of re-authoring the user interface for the user. An ISV can author a credential provider, which is a module that plugs into the LogonUI, to describe the UI and to gather the credential and pass it on to WinLogon. Credential providers are completely transparent to WinLogon.Credential providers are also additive, meaning that users can install multiple credential providers and pick the one that they want to use. Credential providers can be user-selected, event-driven, or both. Multiple credential providers can coexist on Windows Vista and Windows Server 2008 and are not only for third parties. In fact, Windows will ship two credential providers in the box: a credential provider for user name and password and a credential provider for smart card.Additionally, credential providers can be reused within CredUI. That is, the same object that describes and collects credential information on LogonUI can be used to gather the very same credentials in CredUI scenarios.The GINA functionality from Windows XP and Windows Server 2003 has been deprecated and removed from Windows Vista and Windows Server 2008. The GINA modules of applications will not function and must be re-authored using the new authentication model for Windows Vista and Windows Server 2008.

Manifestation

The user will not be able to successfully install custom logon applications.The user will not be able to log on using custom logon applications (using the Windows XP technology) in Windows Vista and Windows Server 2008. These applications might include biometric devices, custom logon UI, or virtual private network (VPN) solutions for remote users with custom logon UI.

Remedies

Leverage new capability:The applications or components that use the GINA technology must be re-authored to use the new logon authentication model for Windows Vista and Windows Server 2008.

Links to Other Resources

For all credential provider information and questions, send e-mail to the Shell Credential Provider alias: credprov@microsoft.com.See Also


Application Compatibility: Read Only Domain Controllers (RODC)

This topic has not yet been rated - Rate this topicRead-Only Domain Controllers (RODC)

Feature Impact

Moderate

Brief Description

A Read-Only Domain Controller (RODC) is a new type of domain controller under the Windows Server 2008 operating system. With an RODC, organizations can easily deploy a domain controller in locations where physical security cannot be guaranteed. An RODC hosts a read-only replica of the database in Active Directory® Domain Services (AD DS) for a given domain.Before the release of Windows Server 2008, if users had to authenticate with a domain controller over a wide area network (WAN), there was no real alternative. In many cases, this solution was not efficient. Branch offices often cannot provide adequate physical security that is required for a writable domain controller. Furthermore, branch offices often have poor network bandwidth when connected to a hub site. This limitation can increase the amount of time required to log on; it can also hamper access to network resources.Beginning with Windows Server 2008, an organization can deploy an RODC to address these problems. As a result, users in this situation can benefit from:Improved security.Faster logon times.More efficient access to resources on the network.

Manifestation

Any application that writes to the Active Directory is potentially impacted by RODCs and might see compatibility issues involving failed writes or failed reads of newly written data.

Remedies

Applications that write data might locate a domain controller using methods that do not differentiate between writable and read-only domain controllers.There are two methods that applications typically use to request the nearest domain controller:Serverless binding, as recommended in Binding to Active Directory Domain ServicesDomain controller Locator callsIn Windows Server 2008, a domain controller Locator call can return any domain controller, including a domain controller running Windows 2000 Server or Windows Server 2003 or a writable or read-only domain controller running Windows Server 2008.Problems can occur if an application needs to write to directory objects and it gets an RODC from calling a serverless bind. In that case, the write operations are referred to a writable domain controller running Windows Server 2008 at the hub site. Depending on the WAN connection to the hub site at that time, the application can fail to connect to the hub and can report errors. The application must also correctly handle these referrals. Even if the write operation succeeds, any subsequent reading of the data that was just written might fail because of inherent latency that is required to replicate this data back to the RODC.Applications that must run on a domain controller should be aware of RODCs. These applications must determine if the domain controller is writable or if it is an RODC. Checking the registry or using OSVERSIONINFOEX, as discussed in OSVERSIONINFOEX Structure, does not distinguish an RODC from a writable domain controller. An RODC still advertises itself as a domain controller.To making this determination, check the supportedCapabilities attribute on the rootDSE class. For more information, see Serverless Binding and RootDSE. The presence of object identifier value 1.2.840.113556.1.4.1920 indicates that the specified domain controller is an RODC.You can also use the DsRoleGetPrimaryDomainInformation function to determine if the domain controller is an RODC. A new flag has been added to the DSROLE_PRIMARY_DOMAIN_INFO_BASIC structure.

Links to Other Resources

Application Compatibility with RODCsThe Future of Active Directory (February 22, 2006) chatThe Future of Windows: Directory Services in Windows Server 2008See Also
http://msdn.microsoft.com/en-us/library/bb757005.aspx

PUSH IT DOWN Compress -Compact

Compact

2 out of 4 rated this helpful - Rate this topicUpdated: April 17, 2012Applies To: Windows Server 2008, Windows VistaDisplays or alters the compression of files or directories on NTFS partitions. If used without parameters, compact displays the compression state of the current directory and the files it contains.For examples of how to use this command, see Examples.Syntaxcompact [/c | /u] [/s[:<Dir>]] [/a] [/i] [/f] [/q] [<FileName>[...]] Parameters

 

ParameterDescription/cCompresses the specified directory or file./uUncompresses the specified directory or file./s[:<Dir>]Applies the compact command to all subdirectories of the specified directory (or of the current directory if none is specified)./aDisplays hidden or system files./iIgnores errors./fForces compression or uncompression of the specified directory or file. /f is used in the case of a file that was partly compressed when the operation was interrupted by a system crash. To force the file to be compressed in its entirety, use the /c and /f parameters and specify the partially compressed file./qReports only the most essential information.<FileName>Specifies the file or directory. You can use multiple file names, and the * and ? wildcard characters./?Displays help at the command prompt.RemarksThe compact command is the command-line version of the NTFS file system compression feature. The compression state of a directory indicates whether files are automatically compressed when they are added to the directory. Setting the compression state of a directory does not necessarily change the compression state of files that are already in the directory.You cannot use compact to read, write, or mount volumes that have been compressed using DriveSpace or DoubleSpace.You cannot use compact to compress file allocation table (FAT) or FAT32 partitions.ExamplesTo set the compression state of the current directory, its subdirectories, and existing files, type:compact /c /s To set the compression state of files and subdirectories within the current directory, without altering the compression state of the current directory itself, type:compact /c /s *.* To compress a volume, from the root directory of the volume, type:compact /c /i /s:\ NoteThis example sets the compression state of all directories (including the root directory on the volume) and compresses every file on the volume. The /i parameter prevents error messages from interrupting the compression process.To compress all files with the .bmp file name extension in the \Tmp directory and all subdirectories of \Tmp, without modifying the compressed attribute of the directories, type:compact /c /s:\tmp *.bmp To force complete compression of the file Zebra.bmp, which was partially compressed during a system crash, type:compact /c /f zebra.bmp To remove the compressed attribute from the directory C:\Tmp, without changing the compression state of any files in that directory, type:compact /u c:\tmp Additional references

|||||||||


OLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:260910 How to obtain the latest Windows 2000 service packWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.There are two possible workarounds available:Use the Expand utility, located in the \I386 folder on the Windows 2000 CD-ROM, to expand the file. To recompress the file, use the Compress utility from the Windows 2000 Resource Kit. When the file has been recompressed, FRS can replicate the file.If you recompress the file, and it does not solve the problem, you can disable the compression process on FRS by changing the following values in the below registry key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\ParametersValue:Compress Staging Files Value Type:dword Value Data: 00000000 <HEX>Note Please ensure to obtain the latest hotfix from the Hotfix server. If a hotfix is being saved, ensure it is refereshed from this server to prevent problems. Note After applying this hotfix three redundant values may be added into the Registry which will need to be fixed in order for IIS to work properly. This should not occur if the above note is followed. But, if this does occur, for more information, please see the following article in the Microsoft Knowledge Base: 296638 Starting Internet Services Manager may cause error messageBack to the top | Give Feedback

Manually compressing the Offline Files cache\database (the %SystemRoot%\CSC folder) works, and files currently stored in the cache are compressed, but newly cached files are not stored in compressed format and previously compressed files become uncompressed after synchronization.Back to the top | Give Feedback

CAUSE

Offline file compression is not directly supported by Offline Files. Windows 2000 writes files in uncompressed format even if the folder is marked for compression. This ensures that a deadlock situation does not occur. Marking the CSC (Client Side Caching) folder to be compressed and leaving it this way can cause a variety of complications ranging from caching update problems to Windows 2000 not responding (hanging) while attempting to access files residing within the cache.Back to the top | Give Feedback

RESOLUTION

To prevent this problem from occurring, do not compress the Offline Files cache/database (the CSC folder).Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.Back to the top | Give Feedback

MORE INFORMATION

If the CSC folder is specifically marked to be compressed, file system calls are made by CSC to ensure that the files get marked as uncompressed. This is done each time a file is accessed within the database.Note that the Offline Files cache\database is hidden by default and cannot be compressed except by an administrator, and should not be directly accessed in such a manner. Doing so may cause the cache to become corrupted. Under typical conditions, a file that currently resides within the cache as compressed is uncompressed after a synchronization update if the file has changes that are written back to the cache.The most common issue that results from compressing the CSC folder is a client computer hanging while attempting to access a cached document while offline.Back to the top | Give Feedback

Properties





Tuesday, January 29, 2013

: PARTITIONS

known issues with the FolderLocation settings in the Windows Vista Unattend.xml file

Article ID: 929831 - View products that this article applies to.Expand all | Collapse all

INTRODUCTION

You can use the FolderLocations settings in the "Microsoft-Windows-Shell-Setup" area of the Windows Vista Unattend.xml file to move the user profiles folder or the program data folder to a non-default target location. The user profiles folder is typically %systemdrive%\Users. The program data folder is typically %systemdrive%\ProgramData.This article describes known issues with the FolderLocations settings in the Unattend.xml file.

MORE INFORMATION

The target location for the user profiles and program data folders can be on a volume other than the system drive as long as the volume meets the following requirements:It must be an NTFS file system volume.It must not be the path of another operating system user profile folder or program data folder.It must not contain any serviceable components.These unattend settings have the following known issues:If you use the FolderLocations unattend settings to move user data or program data to a location other than the %systemdrive% folder, you block upgrades to other versions of Windows Vista or to later releases of Microsoft Windows.If you use the System Preparation Tool (Sysprep) to apply the FolderLocations unattend settings, some system directory junctions do not point to the new target location. The following system directory junctions continue to point to the old locations:C:\Documents and Settings continues to point to C:\Users.C:\ProgramData\Desktop continues to point to C:\Users\Public\Desktop.C:\ProgramData\Documents continues to point to C:\Users\Public\Documents.C:\ProgramData\Favorites continues to point to C:\Users\Public\Favorites.If you use the Windows Vista Setup program to apply the FolderLocations unattend settings, the system directory junctions do not point to the new target location. The following system directory junctions continue to point to the old locations:C:\Documents and Settings continues to point to C:\Users.C:\Users\Default User continues to point to C:\Users\Default.C:\Users\All Users continues to point to C:\ProgramData.If you use the System Preparation Tool to apply the ProfilesDirectory unattend settings, the user profiles of domain users who have previously logged on to the computer are left in the old location. The public profile is also left in the old location.When you use Pkgmgr.exe to service an offline image where the user profiles have been moved to a different drive by using the Microsoft-Windows-Shell-Setup | FolderLocations | ProfilesDirectory answer file entry, you may receive a 0x2 return code.The target location for the user profiles and program data folders can be on a volume other than the system drive as long as the volume meets the following requirements:It must be an NTFS file system volume.It must not be the path of another operating system user profile folder or program data folder.It must not contain any serviceable components.These unattend settings have the following known issues:If you use the FolderLocations unattend settings to move user data to a location other than the %systemdrive% volume some servicing components may not install including but not limited to Critical Updates, Security Updates, Hotfixes and Service Packs.If you use the FolderLocations unattend settings to move user data or program data to a location other than the %systemdrive% folder, you block upgrades to other versions of Windows Vista or to later releases of Microsoft Windows.If you use the System Preparation Tool (Sysprep) to apply the FolderLocations unattend settings, some system directory junctions do not point to the new target location.The following system directory junctions continue to point to the old locations:C:\Documents and Settings continues to point to C:\Users.C:\ProgramData\Desktop continues to point to C:\Users\Public\Desktop.C:\ProgramData\Documents continues to point to C:\Users\Public\Documents.C:\ProgramData\Favorites continues to point to C:\Users\Public\Favorites.If you use the Windows Vista Setup program to apply the FolderLocations unattend settings, the system directory junctions do not point to the new target location.The following system directory junctions continue to point to the old locations:C:\Documents and Settings continues to point to C:\Users.C:\Users\Default User continues to point to C:\Users\Default.C:\Users\All Users continues to point to C:\ProgramData.If you use the System Preparation Tool to apply the ProfilesDirectory unattend settings, the user profiles of domain users who have previously logged on to the computer are left in the old location. The public profile is also left in the old location.

Properties


Drive TypesYou can install Windows to a hard drive, such as a hard disk drive or a solid-state drive. For additional security, you can use hard drives that the factory has pre-encrypted. A single computer may contain multiple drives.Solid-State DrivesA solid-state drive (SSD) is a data storage device that uses solid-state memory to store persistent data. An SSD must have a minimum of 16 gigabytes (GB) of space to install Windows® 8. For more information about drive space and RAM considerations, see Solid State Drive Deployment.Advanced format drivesYou can use some Advanced Format Drives to provide additional drive space.Advanced Format 512 emulation (512e) drives are supported on either BIOS-based or UEFI-based computers.Advanced Format 4K Native (4Kn) drives are supported on UEFI-based computers only.WarningFor Advanced Format 4K Native drives (4-KB-per-sector) drives, the minimum partition size is 260 MB, due to a limitation of the FAT32 file format. The minimum partition size of FAT32 drives is calculated as sector size (4KB) x 65527 = 256 MB. For more information, see How to Configure UEFI/GPT-Based Hard Drive Partitions.Factory-Encrypted Hard DrivesTo help protect your deployment environment, you can use a factory pre-encrypted hard drive to prevent unauthorized access before you install Windows or any other software. For more information, see Factory Encrypted Drives.Multiple Hard DrivesIf you install Windows on a computer that has multiple hard drives, you can use the disk location path to make sure that your images are applied to the intended drives.To do this, use the diskpart SELECT DISK=<disk location path> command to select each drive. For example:SELECT DISK=PCIROOT(0)#PCI(0100)#ATA(C00T00L00)NoteThe system drive might not appear as disk 0 in the DiskPart tool. The system might assign different numbers to drives when you reboot. Different computers that have the same drive configuration can have different disk numbers.For more information, see the following resources:How to Configure Multiple Hard DrivesDiskPart Command line syntaxHard Disk Location Path FormatPartitionsYou can divide your hard drive into multiple partitions. You can create separate system, recovery, Windows, or data partitions.To enhance the security of the Windows partition or a data partition, you can use BitLocker to encrypt the partition. For more information, see BitLocker Drive Encryption.The partition types must match the firmware of the computer. You can install Windows® 8 and Windows Server® 2012 on hard drives that are based on any of the following types of firmware:Basic Input/Output System (BIOS). Uses the Master Boot Record (MBR) partition structure.Extensible Firmware Interface (EFI) (Class 1): Uses the GUID Partition Table (GPT) partition structure.Unified Extensible Firmware Interface (UEFI) Class 2: Uses the GPT partition structure. Also includes a compatibility support module (CSM) that enables you to use BIOS functions, including the MBR partition structure. This module can be enabled or disabled in the firmware.Unified Extensible Firmware Interface (UEFI) Class 3: Uses the GPT partition structure.To determine your system type, consult your hardware manufacturer. For a full description of UEFI Class definitions, see UEFI.org: Evaluating UEFI using Commercially Available Platforms and Solutions.System PartitionsA system partition is a partition that contains the hardware-specific files that are needed to load Windows.By default, during Windows Setup, Windows stores these hardware-specific files in a separate partition. This enables the computer to use the following:Security tools. Some security tools, such as BitLocker, require a separate system partition.Recovery tools. Some recovery tools, such as Windows Recovery Environment (Windows RE), require a separate system partition.Multiple operating systems. If a computer has multiple operating systems, such as Windows® 8 and Windows® 7, the computer displays a list of operating systems. The user can then select which operating system to boot. When the system boot files are on a separate partition, it is easier to remove a Windows partition or replace the partition with a new copy of Windows.For information about how to configure system partitions while you apply images, see How to Capture and Apply Windows, System, and Recovery Partitions.Microsoft Reserved Partition (MSR)The MSR is used on UEFI/GPT systems, to support software components that formerly used hidden sectors.For more information about configuring MSR partitions, see How to Configure UEFI/GPT-Based Hard Drive Partitions.For more information about MSR partitions, see Windows and GPT FAQRecovery PartitionsA recovery partition might include a recovery solution such as Windows RE tools, a recovery image, and/or a third-party recovery tool. A recovery solution can help you reduce your support costs by enabling users to quickly restore a computer's factory settings.We recommend adding Windows RE Tools, system and utility partitions before the Windows partition, because in the event that a full-system recovery is needed, this partition order helps to prevent the recovery tools from overwriting the system and utility partitions. For BIOS/MBR-based systems, we recommend that the Windows RE tools be included in the system partition to reduce the total number of partitions.We recommend adding a partition with a separate recovery image after the Windows partition, because with this partition order, end users who want to reclaim this space for their primary partition may choose to remove this partition and then extend the Windows partition to fill the reclaimed space.Data PartitionsA data partition is a partition that stores user data. A separate data partition can enable easier maintenance for situations where either the primary operating system is likely to be replaced, or when multiple operating systems exist on the same computer, such as, Windows® 8 and Windows® 7. When a computer has multiple hard drives, a data partition may be stored on another drive.WarningFor typical single-drive configurations, we do not recommend that you use a separate data partition. There are two main reasons:The partition may not automatically protect data that is stored outside the user profile folders. For example, a guest user might have access to files in an unprotected data partition.If you change the default location of the user profile folders to any volume other than the system volume, you cannot service your image. The computer may not apply updates, fixes, or service packs to the installation. For a list of known issues related to changing the default folder locations, see Description of known issues with the FolderLocation settings.

See Also

BitLocker Drive Encryption

1 out of 1 rated this helpful - Rate this topicPublished: February 29, 2012Updated: May 31, 2012Applies To: Windows 8, Windows Server 2008 R2, Windows Server 2012This topic highlights the requirements for deploying a Windows® BitLocker® Drive Encryption solution. For more information about BitLocker for Windows® 8, see BitLocker Drive Encryption on the TechNet website.What Is BitLocker Drive Encryption?BitLocker provides offline-data and operating-system protection for your computer. BitLocker helps ensure that data that is stored on a computer that is running Windows® is not revealed if the computer is tampered with when the installed operating system is offline. BitLocker uses a microchip that is called a Trusted Platform Module (TPM) to provide enhanced protection for your data and to preserve early boot-component integrity. The TPM can help protect your data from theft or unauthorized viewing by encrypting the entire Windows volume.BitLocker is designed to offer the most seamless end-user experience with computers that have a compatible TPM microchip and BIOS. A compatible TPM is defined as a version 1.2 TPM that has the BIOS modifications that are required to support the Static Root of Trust Measurement, as defined by the Trusted Computing Group. The TPM interacts with BitLocker to help provide seamless protection when the computer restarts.BitLocker is available in Windows Vista® Enterprise, Windows Vista® Ultimate, Windows® 7 Enterprise, Windows® 7 Ultimate, Windows Server® 2008, Windows® 8, and Windows Server® 2012.The path to the TPM driver file is %WINDIR%\Inf\Tpm.inf. For information about how to add the TPM driver to Windows Preinstallation Environment (Windows PE), see How to Add Device Drivers to an Online Windows PE Image.BitLocker Drive Encryption Partitioning RequirementsBitLocker must use a system partition that is separate from the Windows partition. The system partition:Must be configured as the active partition.Must not be encrypted or used to store user files.Must have at least 100 megabytes (MB) of space.Must have at least 50 MB of free space.May be shared with a recovery partition.For more information about BitLocker partitioning requirements, see Hard Drives and Partitions Overview.

See Also












UNINSTALL SQL Server


Uninstall SQL

Start Registry Editor, and then locate the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallIn the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches the name of the redistributable file. When you see a display name that matches the name of the redistributable file, note the GUID that you clicked in the left pane.For each GUID that you noted in the previous step, run the following command at a command prompt:start /wait msiexec /x {GUID} SKIPREDISTPREREQS=1 /l*v c:\sqlredist_uninstall.log In this command, replace GUID with the GUID that you noted in the previous step.Open the file at C:\Sqlredist_uninstall.log. At the bottom of the file, locate a line that resembles the following line:MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Backward compatibility -- Removal completed successfully.If the uninstallation failed, note the component name and the GUID, and then save the Sqlredist_uninstall.log file.If all the other steps were successful, uninstall the SQL Server Native Client component by using Add or Remove Programs.Do not uninstall the SQL Server Native Client component if you have SQL Server components installed.If all the other steps were successful, uninstall the SQL Server Setup Support Files component by using Add or Remove Programs.If these steps did not uninstall all the components and all the files that are related to the instance of SQL Server, contact product support. For a complete list of product support telephone numbers, see the Microsoft Help and Support Web site.

----**-----------

On a computer that is running SQL Server 2005 along with previous SQL Server versions, Enterprise Manager and other programs that depend on SQL-DMO might be disabled. This can occur in the following situations:Side-by-side installations of any combination of SQL Server 2005, SQL Server 2000, and SQL Server 7.0, where any one or more of these instances is uninstalled.Side-by-side installations of SQL Server 2000 with SQL Server 2005, where SQL Server 2000 is installed after SQL Server 2005.This issue is due to removal of the registration for the SQL Server 2005 SQL-DMO COM library. To re-enable Enterprise Manager and other programs that have SQL-DMO dependencies, register SQL-DMO by running regsvr32.exe sqldmo.dll at the command prompt. For more information, see Troubleshooting an Installation of the SQL Server Database Engine.Before you remove SQL Server 2005 components from a computer that has the minimum required amount of physical memory, you must make sure that the page file size is equal to two times the amount of physical memory. Sometimes, insufficient virtual memory can cause an incomplete removal of SQL Server 2005.If you receive the following error message during SQL Server 2005 Setup, a SQL Server 2005 component was not uninstalled from the computer:A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component. Before you remove SQL Server 2005, follow these steps:Back up your data. You might have databases that you want to save in their present state. You might also want to save changes that were made to the system databases. If either situation is true, make sure that back up the data before you uninstall SQL Server 2005. Alternatively, save a copy of all the data and log files in a folder other than the MSSQL folder. The MSSQL folder is deleted during uninstallation.The files that you must save include the following database files. These files are installed as part of SQL Server 2005:Distmdl.*Master.*Mastlog.*Model.*Modellog.*Msdbdata.*Msdblog.*Mssqlsystemresource.*Northwind.* (This database is an optional installation.)Pubs.*Pubs_log.*Tempdb.*Templog.*ReportServer[$InstanceName] (This is the Reporting Services default database.)ReportServer[$InstanceName]TempDB (This is the Reporting Services default temporary database.)Delete the local security groups. Before you uninstall SQL Server 2005, delete the local security groups for SQL Server 2005 components.Save or rename SQL Server Reporting Services folders. If you use the SQL Server installation together with Reporting Services, save or rename the following folders and subfolders:<drive>\Microsoft SQL Server\Reporting Services<drive>\Microsoft SQL Server\MSSQL\Reporting Services<drive>\Microsoft SQL Server\<SQL Server instance name>\Reporting Services<drive>\Microsoft SQL Server\90\Tools\Reporting ServicesNote:If you used the SSRS configuration tool to configure the installation, the names might differ from the names in this list. Additionally, the databases might be located on a remote computer that is running SQL Server.Delete the Reporting Services virtual directories. Use Microsoft Internet Information Services (IIS) Manager to delete the following virtual directories:ReportServer[$InstanceName]Reports[$InstanceName]Delete the ReportServer application pool. Use IIS Manager to delete the ReportServer application pool.Stop all SQL Server services. We recommend that you stop all SQL Server services before you uninstall SQL Server 2005 components. Active connections can prevent successful uninstallation.Use an account that has the appropriate permissions. Log on to the server by using the SQL Server service account or by using an account that has equivalent permissions. For example, you can log on to the server by using an account that is a member of the local Administrators group.Caution:Incorrectly editing the registry can severely damage your system. Before making changes to the registry, we recommend that you back up any valued data on the computer.Note:You must perform the uninstallation steps listed here in the exact order given.To manually uninstall an instance of SQL Server 2005Make sure that the SQL Server Setup Support Files component is installed.In Add or Remove Programs, make sure that Microsoft SQL Server Setup Support Files appears in the list of installed programs. If Microsoft SQL Server Setup Support Files appears in the list, go to step 2.If Microsoft SQL Server Setup Support Files does not appear in the list, install this component before you continue. To do this, from the SQL Server 2005 installation media, double-click the Servers\setup\sqlsupport.msi file. In step 5 of this procedure, you will uninstall the Microsoft SQL Server Setup Support Files component.At the command prompt, run the following command to uninstall the SQL Server components:%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /Remove Uninstall the SQL Server components one at a time until all the SQL Server components are uninstalled.Note:Add or Remove Programs also runs the ARPWrapper.exe program by using the /Remove option. However, the reference to the ARPWrapper.exe program might have been deleted.If you receive any of the following error messages, see the "If you experience problems" section that follows.Registry Enumeration FailedIf you have an instance of SQL Server that has more than one server component, such as the Database Engine and Analysis Services installed, setup will fail, and you receive the following error message:The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams.This error is expected because of refcounting. A refcount is used to track how many programs use the same .dll file or the same .msi file. When a program is uninstalled, the program decrements the refcount for an .msi file by one. When the last program is uninstalled, the .msi file is deleted. In this case, the .msi file is the SQL Server Setup Support Files component (SqlSupport.msi). If you receive this error message, use one of the following methods to resolve the error:Reinstall the SQL Server Setup Support Files component (SqlSupport.msi) before you uninstall each component in the instance.Temporarily refcount the SqlSupport.msi file to itself. To do this, follow these steps:Obtain the GUID for the Microsoft SQL Server Setup Support Files component. To obtain the GUID, follow steps 1 and 2 from the "If you experience problems" section.Use Registry Editor to create or to modify the following registry key with these values:Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCountValue: UninstallType: REG_SZ Data: {11111111-1111-1111-1111-111111111111},{GUID}Note   GUID is a placeholder for the GUID of the SQL Server support files. For example, the GUID of the English x86 SQL Server support files is as follows:Data: {11111111-1111-1111-1111-111111111111},{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}If you experience problemsIf you experience problems when you try to uninstall the SQL Server components, follow these steps:Start Registry Editor, and then locate the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallIn the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that includes "Microsoft SQL Server 2005." For example, look for the following names:Microsoft SQL Server 2005Microsoft SQL Server 2005 Analysis ServicesMicrosoft SQL Server 2005 Reporting ServicesMicrosoft SQL Server 2005 Notification ServicesMicrosoft SQL Server 2005 Integration ServicesMicrosoft SQL Server 2005 ToolsMicrosoft SQL Server 2005 Books OnlineWhen you see a display name that includes "Microsoft SQL Server 2005," note the GUID that you clicked in the left pane.For each GUID that you noted in the previous step, run the following command at the command prompt:start /wait msiexec /x {GUID} /l*v c:\sql_uninstall.log Notes:In this command, replace GUID with the GUID that you noted in the previous step.If you receive the following error message, contact product support.The setup has encountered an unexpected error in datastore. Please contact a Customer Support representative.For a complete list of product support telephone numbers and for information about support costs, see the support contact information Microsoft Web site.Open the file at C:\Sql_uninstall.log. Approximately 15 lines from the bottom of the file, locate a line that resembles the following:MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Tools -- Removal completed successfully.If the uninstallation failed, note the component name and the GUID, and then save the Sql_uninstall.log file.Use Add or Remove Programs to uninstall the support components in the following order:MSXML 6.0 ParserSQLXML4SQL Server VSS WriterSQL Server 2005 Backward CompatibilityAnything else that is related to SQL Server 2005, except for the SQL Server Native Client component and for the SQL Server Setup Support Files component.If the uninstallation fails for any one of the support components, you might receive the following error message:Setup failed due to missing prerequisitesIf you receive this error message, follow these steps:Start Registry Editor, and then locate the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallIn the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches the name of the redistributable file. When you see a display name that matches the name of the redistributable file, note the GUID that you clicked in the left pane.For each GUID that you noted in the previous step, run the following command at a command prompt:start /wait msiexec /x {GUID} SKIPREDISTPREREQS=1 /l*v c:\sqlredist_uninstall.log In this command, replace GUID with the GUID that you noted in the previous step.Open the file at C:\Sqlredist_uninstall.log. At the bottom of the file, locate a line that resembles the following line:MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Backward compatibility -- Removal completed successfully.If the uninstallation failed, note the component name and the GUID, and then save the Sqlredist_uninstall.log file.If all the other steps were successful, uninstall the SQL Server Native Client component by using Add or Remove Programs.Do not uninstall the SQL Server Native Client component if you have SQL Server components installed.If all the other steps were successful, uninstall the SQL Server Setup Support Files component by using Add or Remove Programs.If these steps did not uninstall all the components and all the files that are related to the instance of SQL Server, contact product



----------

tup Configuration Checker (SCC) in Microsoft SQL Server Setup verifies the value of the counter registry key before SQL Server installation begins. If SCC cannot verify the existing registry key, or if SCC cannot run the lodctr.exe system program, the SCC check will fail, and Setup will be blocked.Incorrectly editing the registry can severely damage your system. Before making changes to the registry, we recommend that you back up any valued data on the computer.To manually set the increment for the counter registry keyOn the Microsoft Windows 2003 or Windows XP desktop, click Start, click Run, type regedit.exe in Open, and then click OK. On Windows 2000, use regedt32.exe The Registry Editor launches.Navigate to the following registry key:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib]"Last Counter"=dword:00000ed4 (5276)"LastHelp"=dword:00000ed5 (5277)The "Last Counter" value from the previous step (5276) must match the maximum value of the "Counter" key from "Perflib\009" in the following registry key, and the "Last Help" value from the previous step (5277) must match the maximum value of the "Help" key from "Perflib\009" in the following registry key:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009]Note that 009 is an example from the English language. The "Last Counter" and "Last Help" values are dynamically assigned by Windows; they will vary from machine to machine.If necessary, modify the value for the "Last Counter" and "Last Help" values in the "\Perflib" key: right-click Last Counter or Last Help in the right-hand pane, click Modify, click Base = "Decimal," set the value in Value data, and then click OK. Repeat for the other key, if necessary, and then close the Registry Editor.Run SQL Server Setup again.See Also

----
Microsoft SQL Server 2005 Setup checks that COM+ is properly configured. If configuration errors are found, Setup will continue, but the following warning appears in the System Configuration Check (SCC) report:"If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup."COM+ errors can result when Microsoft Distributed Transaction Coordinator (MS DTC) is not running or, in the case of Microsoft Cluster Server, if MS DTC is not a clustered resource. COM+ depends upon MS DTC, and the Message Queue Task in Integration Services depends upon COM +. If COM+ errors occur, the Message Queue Task in Integration Services will not be available until the COM+ system is properly configured.To use Message Queuing (also known as MSMQ), ensure that MS DTC is running and properly configured. If SQL Server is installed on a cluster, MS DTC must be a cluster resource.Use the following procedures to reinstall COM+.To install the Component Services snap-inFrom the Windows desktop, click Start and then click Run.In Open, type MMC, and then click OK.In the Console window, click File on the menu bar, and then click Add/Remove Snap-in.In the Add/Remove Snap-in window, click Add.In the Add Standalone Snap-in window, select Component Services from the list of snap-ins, and then click Add.Click Close to close the Add Stand-alone Snap-in window, and then click OK to close the Add/Remove Snap-in window.In the Console Root\Component Services window, expand the Component Services tree. This is where any error message would occur if there was a problem with COM+.Run SQL Server 2005 Setup again. If you get an error message, reinstall COM+.To reinstall COM+From Add or Remove Programs in Control Panel, click Add/Remove Windows Components.In the Windows Components Wizard, click Next without making any selection changes.Click through to complete the wizard, and then run SQL Server 2005 Setup again.See Also


Changing SQL Server Services Accounts After InstallationAfter you have installed SQL Server 2005, use SQL Server Configuration Manager to change the assigned password or other properties of any SQL Server–related service. Each service must be changed individually. The new user account takes effect when the service is restarted.Important:You should not change the passwords for any of the SQL Server service accounts when a failover cluster node is down or offline. If you have to do this, you will need to reset the password again using Configuration Manager when all nodes are back online.The following rights are granted to the accounts:SeServiceLogonRight, which allows the account to run as a service.SeLockMemoryPrivilege, which allows the account to use the AWE memory feature of SQL Server.SeTcbPrivilege, which allows the account to impersonate other accounts.If you are running SQL Server in a failover cluster configuration, permissions are also set for all files in the binary and data installation locations for all nodes in the cluster. Permission is also granted for the service account on the Cluster Object.Caution:If you are running Microsoft Windows 2000 and want to use the Windows 2000 Encrypted File System to encrypt any SQL Server files, you must unencrypt the files before you can change the SQL Server service accounts. If you do not unencrypt the files and then reset the SQL Server service accounts, you cannot unencrypt the files.Changing the current service account for SQL Server to a non-administrator account causes existing full-text catalogs to become inaccessible. Either rebuild and perform a full population of all catalogs belonging to this instance of SQL Server, or switch back to an account with administrator permissions.You can change the SQLServerAgent service account to a non Windows NT 4.0 administrator account. However, the Windows NT 4.0 account must be a member of the sysadmin fixed server role to run SQL Server Agent.For more information, see Setting Up Windows Service Accounts. For information about using the Services add-in for Windows to change SQL Server service accounts, see How to change the SQL Server or SQL Server Agent service account without using SQL Enterprise Manager in SQL Server 2000 or SQL Server Configuration Manager in SQL Server 2005.Windows Passwords ChangesIf your Windows password changes after SQL Server 2005 is installed – e.g., your password expires - you must also revise the user account information for SQL Server services in Windows.To change SQL Server services login account information (Windows 2000)After changing the SQL Server service account information in Control Panel, you must also change the SQL Server service account in SQL Server Configuration Manager. This allows the service account information for Microsoft Search service to remain synchronized as well.Security Note:Setting strong passwords is essential to the security of your system. Always use strong passwords.Important:Although the Microsoft Search service is always assigned to the local system account, the full-text search engine tracks the SQL Server service account in Windows. Full-text search and failover clustering are not available if Windows password changes are not reset.For more information about creating Windows user accounts, granting advanced user rights, setting password expiration, and managing group memberships, see the Windows documentation or User Manager for Domains Help. For Microsoft Windows 2000 users, see Computer Management or Group Policy Editor in the Windows 2000 documentation.See Also

-_-_-----_-

http://msdn.microsoft.com/en-US/library/ms143693(v=sql.90).aspx

Changing SQL Server Services Accounts After InstallationAfter you have installed SQL Server 2005, use SQL Server Configuration Manager to change the assigned password or other properties of any SQL Server–related service. Each service must be changed individually. The new user account takes effect when the service is restarted.Important:You should not change the passwords for any of the SQL Server service accounts when a failover cluster node is down or offline. If you have to do this, you will need to reset the password again using Configuration Manager when all nodes are back online.The following rights are granted to the accounts:SeServiceLogonRight, which allows the account to run as a service.SeLockMemoryPrivilege, which allows the account to use the AWE memory feature of SQL Server.SeTcbPrivilege, which allows the account to impersonate other accounts.If you are running SQL Server in a failover cluster configuration, permissions are also set for all files in the binary and data installation locations for all nodes in the cluster. Permission is also granted for the service account on the Cluster Object.Caution:If you are running Microsoft Windows 2000 and want to use the Windows 2000 Encrypted File System to encrypt any SQL Server files, you must unencrypt the files before you can change the SQL Server service accounts. If you do not unencrypt the files and then reset the SQL Server service accounts, you cannot unencrypt the files.Changing the current service account for SQL Server to a non-administrator account causes existing full-text catalogs to become inaccessible. Either rebuild and perform a full population of all catalogs belonging to this instance of SQL Server, or switch back to an account with administrator permissions.You can change the SQLServerAgent service account to a non Windows NT 4.0 administrator account. However, the Windows NT 4.0 account must be a member of the sysadmin fixed server role to run SQL Server Agent.For more information, see Setting Up Windows Service Accounts. For information about using the Services add-in for Windows to change SQL Server service accounts, see How to change the SQL Server or SQL Server Agent service account without using SQL Enterprise Manager in SQL Server 2000 or SQL Server Configuration Manager in SQL Server 2005.Windows Passwords ChangesIf your Windows password changes after SQL Server 2005 is installed – e.g., your password expires - you must also revise the user account information for SQL Server services in Windows.To change SQL Server services login account information (Windows 2000)After changing the SQL Server service account information in Control Panel, you must also change the SQL Server service account in SQL Server Configuration Manager. This allows the service account information for Microsoft Search service to remain synchronized as well.Security Note:Setting strong passwords is essential to the security of your system. Always use strong passwords.Important:Although the Microsoft Search service is always assigned to the local system account, the full-text search engine tracks the SQL Server service account in Windows. Full-text search and failover clustering are not available if Windows password changes are not reset.For more information about creating Windows user accounts, granting advanced user rights, setting password expiration, and managing group memberships, see the Windows documentation or User Manager for Domains Help. For Microsoft Windows 2000 users, see Computer Management or Group Policy Editor in the Windows 2000 documentation.See Also



SQL Server Agent is a Microsoft SQL Server 2005 component that lets you automate some administrative tasks. SQL Server Agent runs jobs, monitors SQL Server, and processes alerts.The Microsoft Windows account types that are supported and that you can use to run the SQL Server Agent service are listed in the table in the "More information" section. Use SQL Server Configuration Manager to set the service account for SQL Server Agent. For more information, see the "How to set the service startup account for SQL Server Agent (SQL Server Configuration Manager)" topic in SQL Server 2005 Books Online (December 2005 update).To obtain SQL Server 2005 Books Online (December 2005 update), visit the following Microsoft Web site:http://technet.microsoft.com/en-us/sqlserver/bb428874.aspxBack to the top | Give Feedback

MORE INFORMATION

Supported service account types

The following table lists the Windows account types that are supported and that you can use to run the SQL Server Agent service.Service account typeNonclustered serverClustered serverDomain controller (nonclustered)Windows domain account (member of the Windows Administrators group)SupportedSupportedSupportedWindows domain account (nonadministrative)Supported (see limitation 1)Supported (see limitation 1)Supported (see limitation 1)Network Service account (NT AUTHORITY\NetworkService)Supported (see limitations 1, 4, and 5)Not supportedNot supportedLocal user account (nonadministrative)Supported (see limitations 1 and 3)Not supportedNot applicableLocal System account (NT AUTHORITY\System)Supported (see limitation 2)Not supportedSupported (see limitation 2)Local Service account (NT AUTHORITY\LocalService)Not supportedNot supportedNot supported

Limitation 1: When you use a nonadministrative account for multiple-server administration

When you use a nonadministrative account for multiple-server administration, you cannot enlist target servers to a master server, and the following error message may be logged:"The enlist operation failed."To resolve this problem, restart both the SQL Server service and the SQL Server Agent service. For more information, see the following topics in SQL Server 2005 Books Online (December 2005 update):"How to restart an instance of SQL Server (SQL Server Management Studio)""How to restart the SQL Server Agent service (SQL Server Management Studio)"

Limitation 2: When you use the Local System account for multiple-server administration

Multiple-server administration is supported when the SQL Server Agent service runs under the Local System account only when both the master server and the target server reside on the same computer. If you use this configuration, you receive the following message when you enlist target servers to the master server:Ensure the agent start-up account for <target_server_computer_name> has rights to log on as targetServer.You can safely ignore this informational message. The enlistment operation should successfully finish. For more information, see the "Creating a multiserver environment" topic in SQL Server 2005 Books Online (December 2005 update).

Limitation 3: When you use a local user account

Jobs that use proxies will fail if the SQL Server Agent service runs under a local user account and the SQL Server service runs under a different account.To resolve this problem, configure the SQL Server Agent service and the SQL Server service to run under the same local account, and then restart both services. For more information, see the following topics in SQL Server 2005 Books Online (December 2005 update):"How to change the service startup account for SQL Server (SQL Server Configuration Manager)""How to set the service startup account for SQL Server Agent (SQL Server Configuration Manager)""Setting up Windows service accounts"Note Limitation 3 does not apply to Microsoft SQL Server 2005 Service Pack 1 (SP1). For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:913089 How to obtain the latest service pack for SQL Server 2005

Limitation 4: When you use the Network Service account and the Network Service account is a SQL Server user

SQL Server Agent may not start if the following conditions are true:You configure the SQL Server Agent service to run under the Network Service account.The Network Service account was explicitly granted access to log in to an instance of SQL Server as a SQL Server user.To resolve this problem, restart the computer that is running SQL Server. You only have to restart the computer one time.

Limitation 5: When you use the Network Service account and SQL Server Reporting Services is running on the same computer

SQL Server Agent may not start if the following conditions are true:You configure the SQL Server Agent service to run under the Network Service account.SQL Server Reporting Services is also running on the same computer.To resolve this problem, restart the computer that is running SQL Server, and then restart both the SQL Server service and the SQL Server Agent service. You only have to do this one time.Back to the top | Give Feedback





-----

http://msdn.microsoft.com/en-US/library/ms143693(v=sql.90).aspx


http://msdn.microsoft.com/en-US/library/ms183753(v=sql.90).aspx


http://msdn.microsoft.com/en-US/library/ms188980(v=sql.90).aspx

http://msdn.microsoft.com/en-us/library/ms173764(v=sql.90).aspx