Marsden

You can lock it down with Group Policy Editor...

The event log shows an Event ID 2505 error (duplicate name on the network). The error may appear in the event log as either of the following messages: Event ID : 2505 The server could not bind to the transport/device/netbt_<nic driver> because another computer on the network has the same name. The server could not start. -or- Event ID : 2505 The server could not bind to the transport/device/nbf_<nic driver> because another computer on the network has the same name. The server could not start Details Product: windows operating system ID: 8035 Source: browser Version: 5.0 Component: System Event Log Symbolic Name: EVENT_BROWSER_ELECTION_SENT_ROLE_CHANGED Message: The browser has forced an election on network %1 because the Domain Controller (or Server) has changed its role Explanation A network administrator promoted or demoted a domain controller, so another master browser must be elected in order to keep the network functioning. Product: exchange ID: 8015 Source: msadc Version: 6.0 Component: Active Directory Connector Symbolic Name: MSG_LDAP_MODIFY Message: Modifying entry '{object name}' on directory {directory name}. {connection agreement name} User Action No user action is required.

Look up RSoP... Resultant Set of Policies. Use the tool and it will show you where you need to go...

What don't you get?

None of Microsofts distributors sells just COA stickers... You were scammed on eBay! Everyone wants it for next to nothing... And you did this for your company? If you worked for me I'd fire your dumb a** on the spot... <<Yes, its an unbranded COA for OEM XP professional with a CD key on each sticker... so i can use it for my company... just need to know if i can legally get a copy of XP on CDR. There no point in paying for the license sticker and then paying for an official CD on top of that is there?>> There is no shortcut to legality. You purchase the full OEM product in a 3-pack or you are buying conterfit product! A hologramed CD-ROM with the newer Edge to Edge (E2E) copper color which fades to an aluminum band at the edge. You got your bogus conterfiet COAs You don't have your End User License Agreement (EULA) And you don't have a valid Purchase Reciept from an authorized MS distributor... You got nothing...

You can add additional instances of SQL to maximize the use of your hardware, but they will be independent and therefore will not have access to each other's databases. If you are running two instances on two nodes, ensure that one node is able to handle the combined load of both instances to deal with single node failure scenarios. A failover cluster provides improved availability and reliability. The choice to go to a cluster is unrelated to performance... Will there be a chance of a shared-disk clustering option will being available in SQL (Yukon, maybe)? According to MS... no. I would suggest you take a look at Chapter 5 of "Microsoft SQL Server 2000 High Availability".

Are you connected to the Internet? That is where it came from... you accidently clicked on something you shouldn't have... stuff happens...

When was the last time you defragged?

It's called bad spam... just delete them...

go into Group Policy and have clients Search the Network for Shared Printers. Set it to Enabled.

The entries are there in Group Policy under Network Security for enabling or disabling Logon Hours. There is no way to configure Logon Hours except via a server with advanced User properties. It will take a 3rd party tool to do what you want.

What does the Error log say in Event Viewer? That is where you will find your answer... That is why you get the message you get... I'm guessing it doen't like a piece of hardware you have installed. Any yellow markers in Device Manager?

As long as the space where the files were at one time, residing and were not over-written by newer data... yes the data could be recovered by a data recovery company. It is not cheap to employ these services... Could very easlily cost thousands of $$. Where is the backup of these important files?

Upgrading from a Windows NT Domain The Active Directory Installation Wizard simplifies upgrading a Windows NT domain to Windows Server 2003 Active Directory. Active Directory Installation Wizard installs and configures domain controllers, which provide network users and computers access to the Active Directory service. Any member server (except those with restrictive license agreements) can be promoted to domain controllers using the Active Directory Installation Wizard. When promoting member servers to domain controllers, you will define one of the following roles for the new domain controller: • New forest (also a new domain) • New child domain • New domain tree in an existing forest • An additional domain controller in an existing domain For additional information on using the Active Directory Installation Wizard, see the Windows Server 2003 on-screen Help and Support Center. The upgrade process involves the following steps: • Planning and implementing a namespace and DNS infrastructure • Determining forest functionality • Upgrading the server running Windows NT Server 4.0 or earlier primary domain controller • Upgrading any remaining backup domain controllers • Converting groups • Completing the upgrade of the domain • Installing Active Directory client software on older client computers Planning and Implementing a Namespace and DNS Infrastructure Namespace refers to the naming convention that defines a set of unique names for resources in a network, such as Domain Name System (DNS), a hierarchical naming structure that identifies each network resource and its place in the hierarchy of the namespace, and Windows Internet Name Service (WINS), a flat naming structure that identifies each network resource using a single, unique name. DNS is required for Active Directory. DNS is a hierarchical, distributed database that contains mappings of DNS domain names to various types of data, such as IP addresses. DNS enables the location of computers and services by user-friendly names, and it also enables the discovery of other information stored in the database. When setting up a namespace, it is recommended that you first choose and register a unique parent DNS domain name that can be used for hosting your organization on the Internet, for example, microsoft.com. Once you have chosen your parent domain name, you can combine this name with a location or organizational name used within your organization to form other subdomain names. For example, if a subdomain were added, such as itg.example.mydomain.com domain tree (for resources used by the information technology group at your organization), additional subdomain names could be formed using this name. For instance, a group of programmers working on electronic data interchange (EDI) in this division could have a subdomain named edi.itg.example.mydomain.com. Likewise, another group of workers providing support in this division might use support.itg.example.mydomain.com. Prior to beginning the upgrade from Windows NT Server 4.0 to the Windows Server 2003 Active Directory service, ensure that you have designed a DNS and Active Directory namespace and have either configured DNS servers or are planning to have the Active Directory Installation Wizard automatically install the DNS service on the domain controller. Active Directory is integrated with DNS in the following ways: • Active Directory and DNS have the same hierarchical structure. Although separate and implemented differently for different purposes, an organization's namespace for DNS and Active Directory have an identical structure. For example, mydomain.com is both a DNS domain and an Active Directory domain. • DNS zones can be stored in Active Directory. If you are using the Windows Server DNS service, primary zone files can be stored in Active Directory for replication to other Active Directory domain controllers. • Active Directory uses DNS as a locator service, resolving Active Directory domain, site, and service names to an IP address. To log on to an Active Directory domain, an Active Directory client queries its configured DNS server for the IP address of the Lightweight Directory Access Protocol (LDAP) service running on a domain controller for a specified domain. For more information on how Active Directory clients rely on DNS, see “Locating a Domain Controller” in the Windows Server 2003 on-screen Help and Support Center. While Active Directory is integrated with DNS and they share the same namespace structure, it is important to distinguish the basic difference between them: • DNS is a name resolution service. DNS clients send DNS name queries to their configured DNS server. The DNS server receives the name query and either resolves the name query through locally stored files or consults another DNS server for resolution. DNS does not require Active Directory to function. • Active Directory is a directory service. Active Directory provides an information repository and services to make information available to users and applications. Active Directory clients send queries to Active Directory servers using LDAP. In order to locate an Active Directory server, an Active Directory client queries DNS. Active Directory requires DNS to function. For more information on DNS configuration, see the Windows Server 2003 on-screen Help and Support Center. Determining Forest Functionality Forest functionality determines the type of Active Directory features that can be enabled within the scope of a single forest. Each forest functional level has a set of specific minimum requirements for the version of operating system that domain controllers throughout the forest can run. For example, the Windows forest functional level requires that all domain controllers be running Windows Server 2003 operating systems. In the scenario where you are upgrading your first Windows NT domain so that it becomes the first domain in a new Windows Server 2003 forest, it is recommended that you set the forest functional level to “Windows interim.” (You will be prompted during the upgrade.) This level contains all the features used in the Windows 2000 forest functional level and also includes two important advanced Active Directory features: • Improved replication algorithms made to the intersite topology generator • Replication improvements made to group memberships The Windows interim functional level is an option when upgrading the first Windows NT domain to a new forest and can be manually configured after the upgrade. For more information about how to manually set this functional level, see the Microsoft Windows Resource Kits Web site at http://www.microsoft.com/windows/reskits/. The Windows interim forest functional level only supports domain controllers running Windows and Windows NT, not domain controllers running Windows 2000. Servers running Windows 2000 cannot be promoted to a domain controller in a forest where the forest functional level has been set to Windows interim.

Have you checked the Hardware Compatability List for Server 2003? The driver you need may not exist for Win2k3... Which is usually the reason Datacenter ships only on approved OEM hardware...

Your system got slow because you are running a very slow (by todays standards) CPU. I would seriously consider a faster CPU, at least double your RAM. and think about a newer video card. I'm not suggesting it won't work, it will, but it will be dog slow...

If chkdsk /r (implies the /F switch as well) can't fix whatever is wrong, then I seriuosly doubt any 3rd party tool will fair better. Sometimes you have to run it multiple time till it comes up clean... it has always worked for me.

I have had no issues with Outlook 2003 with and without Office 2003 SP1 on XP SP1 or SP2 but then I am using Exc 2003 as a mail server. I would look to issues with the OS and not the Office programs themselves...

True Firewalls are hardware based... with stateful packet inspection, and can ONLY be configured once they are completely removed from your network. That means that all software firewalls don't meet those qualifications... meaning they are insecure by their very nature. If the software can be installed by a user, it can be uninstalled by a hacker...

Server services are always online... Your server could be running a couple of different services or hundreds... it all depends on how much hardware power you have... You can be on logged on locally as well as supporting remote VPN connections...

It just means it is compressed...

The Network Install Package covers ALL XP products lines... Pro, Home, Media Center, and Tablet versions.

There is no 2nd Repair Option to fix a Service Pack. There has been the 2nd Repait Option ever since Windows 2000. All it does is replace all system files with their orginals without reformating or overwriting your registry settings. All installed programs still function as before. Your machine is set back to it's orginal install and you must reinstall all patches and service packs... in this case SP2, since it now superceeds SP1a.

You are running a trial version...

Yes Employ the 2nd Repair Option after booting from your XP CD. Re-install SP2...