Step 1: Verify the Installation of the SMTP Service
In Control Panel, open Add/Remove Programs, click Add/Remove Windows Components. Click the Internet Information Services (IIS) component, click Details, and then verify that the SMTP Service check box is selected.
If it is not selected, click to select it, click OK, and then follow the installation directions that are displayed.
Step 2: Configure the SMTP Service to Relay for Internal Domains
Depending on the scenario, it may be necessary to configure the SMTP service to relay inbound messages for your internal domains.
1. Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
2. Expand the tree under the server name, and then expand the Default SMTP Virtual Server. By default, you should have a Local (Default) domain with the fully qualified domain name of the server.
3. Configure the domain for inbound:
a. Right-click the Domains icon, click New, and then click Domain.
b. Click Remote, click Next, and then type the forwarder.yourcompany.com in the Name box. Click Finish.
Configure the domain for relay
1. In the properties for the domain that you just created, click to select the Allow the Incoming Mail to be Relayed to this Domain check box.
2. If this is being set up for a internal domain, you should specify the server that receives e-mail for the domain name by the IP address in the Route domain dialog box.
3. Click the forward all e-mail to smart host option, and then type the IP address of the server that is responsible for e-mail for that domain in square brackets.
Note: Typing the IP address of the server in brackets is necessary so that the server recognizes this is an IP address and not to attempt a DNS lookup.
Step 3: Specify the Hosts That You Want to Openly Relay to All Domains
Note:
Anyone can send to the domains that you specified in Step 2.
This step is for hosts, which are most likely your internal servers that would need to send to all domains on the Internet. It is not recommended to not have any restrictions because anyone can use your server as an open relay. It is recommended to only allow the minimum, necessary hosts to openly relay to all domains. To do so:
1. Open the properties of the Default SMTP Virtual Server.
2. On the Access tab, click Relay.
3. Click Only the list below, make sure the list is empty. Check the checkbox before “Allow all computers which successfully authenticate to relay, regardless of the list above”.
Showing posts with label Microsoft. Show all posts
Showing posts with label Microsoft. Show all posts
Thursday, March 26, 2009
Turn on ASP support in IIS (Windows 2003 server)
Turn on ASP support in IIS Administration.
Open IIS Manager
- click Web Sites
- open
- Right click
- Select Properties
- Select Tab ‘Home Directory”
- Click ‘Configuration Button”
- Verify that .ASP and .ASPX are in ‘Application Extensions’ list. Otherwise add them.
- Click OK to close.
Open IIS Manager
- click Web Sites
- open
- Right click
- Select Properties
- Select Tab ‘Home Directory”
- Click ‘Configuration Button”
- Verify that .ASP and .ASPX are in ‘Application Extensions’ list. Otherwise add them.
- Click OK to close.
Configure SMTP on IIS (Windows 2003)
Step 1: Verify the Installation of the SMTP Service
In Control Panel, open Add/Remove Programs, click Add/Remove Windows Components. Click the Internet Information Services (IIS) component, click Details, and then verify that the SMTP Service check box is selected.
If it is not selected, click to select it, click OK, and then follow the installation directions that are displayed.
Step 2: Configure the SMTP Service to Relay for Internal Domains
Depending on the scenario, it may be necessary to configure the SMTP service to relay inbound messages for your internal domains.
Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
Expand the tree under the server name, and then expand the Default SMTP Virtual Server. By default, you should have a Local (Default) domain with the fully qualified domain name of the server.
Configure the domain for inbound:
Right-click the Domains icon, click New, and then click Domain.
Click Remote, click Next, and then type the forwarder.gm.com in the Name box. Click Finish.
Configure the domain for relay
In the properties for the domain that you just created, click to select the Allow the Incoming Mail to be Relayed to this Domain check box.
If this is being set up for a internal domain, you should specify the server that receives e-mail for the domain name by the IP address in the Route domain dialog box.
Click the forward all e-mail to smart host option, and then type the IP address of the server that is responsible for e-mail for that domain in square brackets. IP of forwarder.yourcompany.com is:
[168.208.12.12]
Note: Typing the IP address of the server in brackets is necessary so that the server recognizes this is an IP address and not to attempt a DNS lookup.
Click OK.
In Control Panel, open Add/Remove Programs, click Add/Remove Windows Components. Click the Internet Information Services (IIS) component, click Details, and then verify that the SMTP Service check box is selected.
If it is not selected, click to select it, click OK, and then follow the installation directions that are displayed.
Step 2: Configure the SMTP Service to Relay for Internal Domains
Depending on the scenario, it may be necessary to configure the SMTP service to relay inbound messages for your internal domains.
Click Start, point to Programs, click Administrative Tools, and then click Internet Services Manager.
Expand the tree under the server name, and then expand the Default SMTP Virtual Server. By default, you should have a Local (Default) domain with the fully qualified domain name of the server.
Configure the domain for inbound:
Right-click the Domains icon, click New, and then click Domain.
Click Remote, click Next, and then type the forwarder.gm.com in the Name box. Click Finish.
Configure the domain for relay
In the properties for the domain that you just created, click to select the Allow the Incoming Mail to be Relayed to this Domain check box.
If this is being set up for a internal domain, you should specify the server that receives e-mail for the domain name by the IP address in the Route domain dialog box.
Click the forward all e-mail to smart host option, and then type the IP address of the server that is responsible for e-mail for that domain in square brackets. IP of forwarder.yourcompany.com is:
[168.208.12.12]
Note: Typing the IP address of the server in brackets is necessary so that the server recognizes this is an IP address and not to attempt a DNS lookup.
Click OK.
Install SMTP service under Windows Server 2003
The version of Microsoft IIS that ships with Windows 2003 contains a service that you can use to deliver mail using SMTP. To install this SMTP service, perform the following steps:
1. Start the Control Panel Add/Remove Programs applet.
2. Click Add/Remove Windows Components.
3. After the Windows Components Wizard appears, select Applications Server and click Details.
4. Select Internet Information Services (IIS), then click Details.
5. Select SMTP Service, then click OK as this figure shows.
6. Continue to click OK to close all other dialog boxes until you're back at the Windows Components Wizard page, then click Next.
Windows 2003 will copy the files required for the SMTP service (you might be prompted to insert the installation CD-ROM) and configure the service. You can also install the SMTP service through the E-mail Services tool, which is a POP3 component that automatically installs SMTP. Windows 2003 configures the SMTP service to use a default server, and you can use the IIS Manager to modify the server settings.
Determine MDAC version
Determining which version of MDAC is installed on a computer at any given time presents certain difficulties because individual MDAC files may have been replaced by an errant installer, which complicates the situation. Component Checker is probably the most useful tool that is available for verifying MDAC installations. Component Checker is available for download from Data Access and Storage Developer Center MDAC Downloads.
Install and Use the Component Checker Tool
The most reliable way to determine which version of MDAC is installed is to compare the version number of each MDAC DLL file to a list of the DLL files that are shipped with each MDAC version. The Component Checker can help you to do this. It checks the files on the computer, compares them to a list from each version of MDAC, and reports the closest match.To install Component Checker, follow these steps:
1. Browse to the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en)
2. Click the link to download Component Checker. When you are prompted by the browser, save Cc.exe (a self-extracting executable file) to the desktop.
3. On the desktop, double-click Cc.exe; this extracts the Component Checker files and installs to the default location, C:\Comcheck.
To use Component Checker to check the MDAC version, follow these steps:
1. From the Start menu, click Run.
2. In the Open text box, type c:\comcheck\comcheck.exe and then click OK.
3. In the Component Checker - Choose Analysis Type dialog box, select Perform Analysis of your machine and automatically determine the release version, and then click OK.
4. The program attempts to identify the MDAC version on your computer by scanning all of the core MDAC files and registry settings. This process normally takes several minutes. When finished, you should receive the following message:
The MDAC version that is closest to the version on your computer is 'XXXX'.
5. Click OK.
6. A summary of the Component Checker scan appears. Note that the Dir, FileDescription, and FileSize errors can be safely ignored.
Check the Version Information Stored in the Registry
Although not the most reliable way to check the MDAC version, checking the registry for the version information is an easy way to double-check this information (if you are not experiencing any MDAC-related issues).The version information is found in the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
To check the registry, follow these steps:
1.On the Start menu, click Run.
2.In the Open text box, type regedit and then click OK; this starts Registry Editor.
3.In the Navigation pane, drill-down to the following path:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess
4.In the Details pane, look in the Name column for FullInstallVer and Version. Each of these keys will have corresponding version information in the Data column.
5.When finished, click Exit on the Registry menu to close Registry Editor.
1. Start the Control Panel Add/Remove Programs applet.
2. Click Add/Remove Windows Components.
3. After the Windows Components Wizard appears, select Applications Server and click Details.
4. Select Internet Information Services (IIS), then click Details.
5. Select SMTP Service, then click OK as this figure shows.
6. Continue to click OK to close all other dialog boxes until you're back at the Windows Components Wizard page, then click Next.
Windows 2003 will copy the files required for the SMTP service (you might be prompted to insert the installation CD-ROM) and configure the service. You can also install the SMTP service through the E-mail Services tool, which is a POP3 component that automatically installs SMTP. Windows 2003 configures the SMTP service to use a default server, and you can use the IIS Manager to modify the server settings.
Determine MDAC version
Determining which version of MDAC is installed on a computer at any given time presents certain difficulties because individual MDAC files may have been replaced by an errant installer, which complicates the situation. Component Checker is probably the most useful tool that is available for verifying MDAC installations. Component Checker is available for download from Data Access and Storage Developer Center MDAC Downloads.
Install and Use the Component Checker Tool
The most reliable way to determine which version of MDAC is installed is to compare the version number of each MDAC DLL file to a list of the DLL files that are shipped with each MDAC version. The Component Checker can help you to do this. It checks the files on the computer, compares them to a list from each version of MDAC, and reports the closest match.To install Component Checker, follow these steps:
1. Browse to the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en)
2. Click the link to download Component Checker. When you are prompted by the browser, save Cc.exe (a self-extracting executable file) to the desktop.
3. On the desktop, double-click Cc.exe; this extracts the Component Checker files and installs to the default location, C:\Comcheck.
To use Component Checker to check the MDAC version, follow these steps:
1. From the Start menu, click Run.
2. In the Open text box, type c:\comcheck\comcheck.exe and then click OK.
3. In the Component Checker - Choose Analysis Type dialog box, select Perform Analysis of your machine and automatically determine the release version, and then click OK.
4. The program attempts to identify the MDAC version on your computer by scanning all of the core MDAC files and registry settings. This process normally takes several minutes. When finished, you should receive the following message:
The MDAC version that is closest to the version on your computer is 'XXXX'.
5. Click OK.
6. A summary of the Component Checker scan appears. Note that the Dir, FileDescription, and FileSize errors can be safely ignored.
Check the Version Information Stored in the Registry
Although not the most reliable way to check the MDAC version, checking the registry for the version information is an easy way to double-check this information (if you are not experiencing any MDAC-related issues).The version information is found in the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
To check the registry, follow these steps:
1.On the Start menu, click Run.
2.In the Open text box, type regedit and then click OK; this starts Registry Editor.
3.In the Navigation pane, drill-down to the following path:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess
4.In the Details pane, look in the Name column for FullInstallVer and Version. Each of these keys will have corresponding version information in the Data column.
5.When finished, click Exit on the Registry menu to close Registry Editor.
Friday, March 20, 2009
Microsoft SharePoint Services
2007 Microsoft Office System
- WSS 3.0 – Windows SharePoint Services V3.0
- MOSS – Microsoft Office SharePoint Server
- MOSS is part of 2007 Microsoft Office System (Desktop App: Access, Accounting, Communicator, Excel, FrontPage, Groove, InfoPath, OneNote, Outlook, PowerPoint, Project, Publisher, SharePoint Designer, Visio, Word; Servers: Forms, Groove, Live Communications, PerformancePoint, Project Portfolio, Project, SharePoint, SharePopint Server Search )
Operating System services:
- ASP.NET
- Windows Workflow Foundation
Enterprise Content Management
- More just managing documents in a library
- Per-item level permissions, recycle bins, full major/minor versioning, content types
Tiers
- Tier 1: Web Front End (WFE)
- Tier 2: Application tier
- Tier 3: Database tier
Deployment
- WSS 3.0 on single-server
- Onto multiple servers (server farm)
- Single server can host (WFE, application, database)
Site Framework
- Web-based application (under IIS)
- Site Collection (Sites)
- Site
Pages
- Master Pages
- Page Layouts
- Content Pages
Site
- Site Definitions – initial lists, libraries, views, Web Parts and pages (defined in XML files under SiteTemplates)
- Site Templates
- Features: Feature.XML
Storage
- Lists
- Libraries (physical document column)
- Different types (content type) of document in single libraries
- Library documents can be opened and saved directly from Office 2007 application
Administration
- Folders
- Recycle Bin
- AutoCopy
- List column limitation is 2000
- Generally, if display more than 1000 itemns in a single view, need to consider indexing certain columns
Versioning
- Major
- Minor
- Libraries support check-in and check-out
List Level Permission
- Manage Lists
- Override Check Out
- Add Items
- Edit Items
- Delete Items
- View Items
- Approve Items
- Open Items
- View Versions
- Delete Versions
- Create Alerts
- View Application Pages
Site Permission
- Manage Permissions
- View Usage Data
- Create Sbsites
- Manage Web Site
- Add and Customize Pages
- Apply Themes and Borders
- Apply Style Sheets
- Create Groups
- Browse Directories
- Use Self-Service Site Creation
- View Pages
- Enumerate Permissions
- Browse User Information
- Manage Alerts
- Use Remote Interfaces
- Use Client Integration Features
- Open
- Edit Personal User Information
Default Groups
- [Site name] Visitors - Read
- [Site name] Members – Contribute
- [Site name] Owners – Full Control
Authentication
- Active Directory
- LDAP
- SQL database
- Pluggable authentication is possible via ASP.NET provider model
- WSS 3.0 – Windows SharePoint Services V3.0
- MOSS – Microsoft Office SharePoint Server
- MOSS is part of 2007 Microsoft Office System (Desktop App: Access, Accounting, Communicator, Excel, FrontPage, Groove, InfoPath, OneNote, Outlook, PowerPoint, Project, Publisher, SharePoint Designer, Visio, Word; Servers: Forms, Groove, Live Communications, PerformancePoint, Project Portfolio, Project, SharePoint, SharePopint Server Search )
Operating System services:
- ASP.NET
- Windows Workflow Foundation
Enterprise Content Management
- More just managing documents in a library
- Per-item level permissions, recycle bins, full major/minor versioning, content types
Tiers
- Tier 1: Web Front End (WFE)
- Tier 2: Application tier
- Tier 3: Database tier
Deployment
- WSS 3.0 on single-server
- Onto multiple servers (server farm)
- Single server can host (WFE, application, database)
Site Framework
- Web-based application (under IIS)
- Site Collection (Sites)
- Site
Pages
- Master Pages
- Page Layouts
- Content Pages
Site
- Site Definitions – initial lists, libraries, views, Web Parts and pages (defined in XML files under SiteTemplates)
- Site Templates
- Features: Feature.XML
Storage
- Lists
- Libraries (physical document column)
- Different types (content type) of document in single libraries
- Library documents can be opened and saved directly from Office 2007 application
Administration
- Folders
- Recycle Bin
- AutoCopy
- List column limitation is 2000
- Generally, if display more than 1000 itemns in a single view, need to consider indexing certain columns
Versioning
- Major
- Minor
- Libraries support check-in and check-out
List Level Permission
- Manage Lists
- Override Check Out
- Add Items
- Edit Items
- Delete Items
- View Items
- Approve Items
- Open Items
- View Versions
- Delete Versions
- Create Alerts
- View Application Pages
Site Permission
- Manage Permissions
- View Usage Data
- Create Sbsites
- Manage Web Site
- Add and Customize Pages
- Apply Themes and Borders
- Apply Style Sheets
- Create Groups
- Browse Directories
- Use Self-Service Site Creation
- View Pages
- Enumerate Permissions
- Browse User Information
- Manage Alerts
- Use Remote Interfaces
- Use Client Integration Features
- Open
- Edit Personal User Information
Default Groups
- [Site name] Visitors - Read
- [Site name] Members – Contribute
- [Site name] Owners – Full Control
Authentication
- Active Directory
- LDAP
- SQL database
- Pluggable authentication is possible via ASP.NET provider model
Wednesday, March 18, 2009
WCF
Overview
- Framework for Service-Oriented application
- API in System.ServiceModel namespace
- Unify distributed system technologies
- Single Window programming model for SOA
- Utilize .NET Framework
Fundamentals
- Set of APIs for sending messages between clients and services
- Unifies the features of COM+, .NET Remoting, MSMQ, Enterprise Services, Web Services(ASMX) and Web Service Enhancements(WSE)
- Interoperability with existing DSTs
- Built on .NET Framework
- .NET Framework through System.Net.Sockets.Socket and System.Messaging.MessageQueue etc.
- Framework for Service-Oriented application
- API in System.ServiceModel namespace
- Unify distributed system technologies
- Single Window programming model for SOA
- Utilize .NET Framework
Fundamentals
- Set of APIs for sending messages between clients and services
- Unifies the features of COM+, .NET Remoting, MSMQ, Enterprise Services, Web Services(ASMX) and Web Service Enhancements(WSE)
- Interoperability with existing DSTs
- Built on .NET Framework
- .NET Framework through System.Net.Sockets.Socket and System.Messaging.MessageQueue etc.
Architecture
Architecture - Contracts
- Data Contract – Paremeters in message consumed by a service (metadata datatype)
- Message Contract – Message structure used for communication
- Service Contract – Service name, namespace and attributes
- Operation Contract – Member method of Service Contract interface returning operation type and parameters
- Service Runtime – Behaviors only occurred during operation
- Messaging – Formats and Message Exchange Patterns of the data
- Activation & Hosting – Either self-hosted or hosted in the contect of another application (EXE, Windows Service, COM+ component or IIS module)
- Message Contract – Message structure used for communication
- Service Contract – Service name, namespace and attributes
- Operation Contract – Member method of Service Contract interface returning operation type and parameters
- Service Runtime – Behaviors only occurred during operation
- Messaging – Formats and Message Exchange Patterns of the data
- Activation & Hosting – Either self-hosted or hosted in the contect of another application (EXE, Windows Service, COM+ component or IIS module)
ABCs
- Address – Identify Service
- Bindings – “Canned” Policies
- Contract – Expose Service
- Bindings – “Canned” Policies
- Contract – Expose Service
Subscribe to:
Posts (Atom)
Posts
