The SAP Connector is one of several "Solution Starters" that Microsoft offers for Office Project Server 2003. More information on the add-ons for Project Server is available at:
http://msdn.microsoft.com/office/understanding/project/solution/default.aspx
Asset Management is a recognised accountancy process that includes depreciation accounting. Asset Management systems maintain details on assets above a certain value, their business unit and their location. Configuration Management also maintains relationships between assets, which Asset Management usually does not. Some organisations start with Asset Management and then move on to Configuration Management.
Network Protection
Outlook 2003 Q883606
OL2002 Q305572 OL2000 Q304849
IE add-on mgr and Pop-up blocking
OWA Q883575
S-MIME Q883543
1. Design
Connection Speed:
slow link is defined as a link with bandwidth between 19.2 kilobits and 128 kilobits (below 19.2, we need to use SMTP replication);a T1 line would be considered a medium-speed connection;a high-speed connection would be 10 megabits or higher
Centralized or Decentralized:
1.1.Logical Design
1.1.1. Forest design
http://www.microsoft.com/downloads/details.aspx?familyid=6cde6ee7-5df1-4394-92ed-2147c3a9ebbe&displaylang=en
1.1.2. Domain design
Based on the allocation of one percent of bandwidth to Active Directory, the Windows Server 2003 Deployment Kit does not recommend hosting 100,000 users in a single domain where WAN links will be used for replication, unless the minimum link speed in the domain is at least 1,500 Kbps.
Domain controllers replicate Group Policies to one another using File Replication service (FRS) replication. Due to the way FRS functions, it is best not to exceed 1,200 domain controllers per domain. This means that if you are planning on placing one domain controller in each branch office location, you should limit the number of domain controllers to less than 1,200 locations per domain. This number—1,200 domain controllers—is not a hard limit in Windows Server 2003. Rather, it is the recommended maximum related to the ability of FRS to recover SYSVOL should the SYSVOL become unavailable.
1.1.3. OU design
1.2. Physical Design
1.2.1 # of sites
In a branch office environment, you typically create sites for to fulfill three functions:
• A site that includes the data center. This site is often referred to as the hub.
• Sites for the branches. Typically a separate site will be used to represent each branch office.
• A site that you use as the staging area to prepare servers for deployment to branch offices.
1.2.2 DC placement
For each domain in the forest you must have at least two domain controllers that can be located in any of the data centers.
You might place additional domain controllers in the hub site for the following reasons:
• To provide a failover mechanism
• To distribute specialized roles (operations master, global catalog, DNS).
• To centralize mission-critical roles
In addition to the two domain controllers required for each domain in the hub site, you must include bridgehead servers. Bridgehead servers are domain controllers in the hub site that are responsible for communicating with domain controllers in the branch sites.
If you have more than 50 users in the branch office, you should consider placing a domain controller in that location. The services that you deploy in a branch office also contribute to whether or not you need to place a domain controller in that location.
it is recommended that all operations master role holders be located in the data center and not in any branch office location
1.2.3 config replication
1.3. DNS design
All domain controllers are DNS servers.
DNS client settings on all domain controllers in the forest are configured to point to themselves as their primary DNS server and at least one other domain controller in the same domain as the alternate DNS server.
All zones representing Active Directory domains are Active Directory-integrated.
Site topology and rep design
Capacity planning
Scalability should not be an issue in a single-forest model. If you have less than 5,000 branches and less than 100,000 users, you should be able to use a single-forest model, provided it meets your isolation and autonomy requirements. This guide uses a single-forest model to host a 5,000-branch environment. If you have more than 5,000 branches or more than 100,000 users, consider deploying multiple forests. If you decide to deploy a single forest into an environment with more than 5,000 branches or 100,000 users, additional testing is required.
Monitoring design:
In a branch office environment, it is recommended that you use MOM to monitor the domain controllers in the hub, and Branch Office Monitor to monitor the domain controllers in the branch offices.
2. Deploment
deploy and monitor non-branch domains
deploy and monitor branch domain in hub site
deploy and monitor staging site
deploy and monitor branch site
Guide 1.1
http://www.microsoft.com/downloads/details.aspx?FamilyId=9353A4F6-A8A8-40BB-9FA7-3A95C9540112&displaylang=en