· Experts Exchange > Questions > the account name is invalid or does not exist, or the password is invalid for the account name specified. I am trying to connect the Reporting Services Configuration Manager installed on my application server to a ReportServer database located on another server. I am. · Hi Guys and Girls, I have 250 users all on my exchange 2007 box. All users can send via OWA with no problem what-so-ever. I have one user that needs to use. Share an Outlook calendar with other people. If you have an Office 3. Exchange- based account, you can also send a sharing invitation to other users so they can view your calendar in their own Calendar list. If you’re using Office 3. Outlook or Outlook Web App: Want to publish your Office 3. Watch this video: In this article. Share your calendar in an email. Share your Office 3. Exchange- based calendar with people inside or outside your organization. Share your calendar with people inside your organization. Share your calendar with people outside your organization. Change permissions after you have shared your calendar with other people. Share a calendar by publishing it to a web page. Share your calendar in an email. Click Calendar. Click Home > E- mail Calendar. In the Calendar and Date Range boxes, pick the calendar and time period you want to share. For example, choose Today only or for the Next 7 days. Set any other options you want, and then click OK. In the new email that opens, add who you want the message to go to in the To field, add a message if you want, and click Send. The person you sent your calendar to will see a snapshot of your calendar in the message. The message also includes an attached i. Calendar (. ics) file that they can open in Outlook or another calendar program. When the recipient clicks the i. Calendar file, Outlook displays the file as a new calendar that they can view side- by- side with their calendar. They can drag appointments or meetings between the two calendars, and find a time that works for both of you. Share your Office 3. Exchange- based calendar with people inside or outside your organization. If you have an Office 3. Microsoft Exchange- based email account, and you want to share your calendar with someone who is inside or outside your organization, you can give them permissions to view your calendar. Share your calendar with people inside your organization. Click Calendar. Click Home > Share Calendar. In the email that opens, type the name of the person in your organization that you want to share your calendar with in the To box. In Details, specify the level of details that you want to share with the person in your organization, and then click Send. The person in your organization receives the sharing invitation in email, and then clicks Open this calendar. The shared calendar displays in the person’s Calendar list. Share your calendar with people outside your organization. Click Calendar. Click Home > Share Calendar. In the email that opens, type the email address for the person outside of your organization that you want to share your calendar with in the To box. In Details, specify the level of details that you want to share with the person outside of your organization, and then click Send. If the following error displays when you try to send your sharing invitation, you have tried to share more details than is supported by the settings in your organization. If this occurs, under Details, choose to share a different level of details. Only an admin in your organization can change the sharing policy settings for your organization. For more information, see the end of this section. The person in your organization receives the sharing invitation in email, and then clicks Open this calendar. The shared calendar displays in the person’s Calendar list. If you receive an error when you try to share more details that are supported by the sharing policy settings in your organization, contact the person that manages your email account. Change permissions after you have shared your calendar with other people. You can change calendar sharing permissions. Click Calendar. Click Home > Calendar Permissions. On the Permissions tab, make any changes to the calendar sharing permissions. Click OK. Share a calendar by publishing it to a web page. If you have access to a web server that supports the World Wide Web Distributed Authoring and Versioning (Web. DAV) protocol, you can publish your calendar there. Note: Not sure if your server supports Web. DAV? Your server administrator or internet service provider (ISP) should be able to tell you. Click Calendar. Click Home > Publish Online > Publish to Web. DAV Server. Notes: If your email account uses Exchange, you will see Publish This Calendar, instead of the option to publish to a Web. DAV server. This lets you publish your calendar directly to an Exchange Server. In the window that opens, select the publishing options you want, and click Start Publishing. If you're using Office 3. Web. DAV server, but you must first remove {Anonymous: Calendar. Sharing. Free. Busy. Simple} from the sharing policy. This will prevent you from publishing your calendar to Exchange in the future, however. In the Location box, enter the location of the Web. DAV server, select any other publishing options you want, and then click OK. See also. Sharing your calendar in Outlook Web App. You can share calendar information with other people by using Outlook 2. By email. With Microsoft Exchange Server accounts. By publishing a calendar online. What do you want to do? Share calendars by email. Share calendars using a Microsoft Exchange Server account. Share a calendar by publishing it online. Share calendars by email. Calendars shared by email arrive in the recipient’s Inbox as email message attachments, with a Calendar Snapshot in the message body. You can edit the Calendar Snapshot before sending. For example, you can change fonts or highlight days or appointments. To send a calendar by email: On the Home tab, in the Share group, click E- mail Calendar. In the Calendar box, click the calendar that you want to send. In the Date Range box, click the time period that you want the calendar to show. Enter or select any other options that you want, and then click OK. An Outlook 2. 01. Calendar by email can choose to open the Calendar Snapshot in Outlook. Doing so can display the Calendar Snapshot and the recipient’s current calendar in side- by- side mode or calendar overlay mode. Share calendars using a Microsoft Exchange Server account. Microsoft Exchange Server enables calendar sharing with others who have Exchange accounts. Your calendars can be viewed only by others to whom you have granted permissions. If the other person whose calendar you want to open has not granted you permission to view it, Outlook prompts you to ask the person for the permission that you need. After you access a shared calendar for the first time, the calendar is added to the Shared Calendars list in the Navigation Pane, where you can access it the next time that you want to view it. To share your calendar with another Exchange user: On the Home tab, in the Share group, click Share Calendar. In the Sharing Invitation that appears, enter the person who you want to share with in the To box. Enter or select any other options that you want, just as if you were sending an email message. The recipient sees an email notification that you have shared your calendar. You can also request that the recipient share his or her Exchange Calendar with you. Tip: If you want to share a calendar that you created that is not your default Calendar, in the Navigation Pane, right- click the calendar name, and then click Share calendar name. Share a calendar by publishing it online. You can publish your default Outlook 2. Calendar to the Internet, which enables more people to view it. Publishing an Internet Calendar requires neither the publisher nor the user to use an Exchange account. Publish to Outlook. You can share your Outlook calendar with others by publishing it on Outlook. To share your Outlook calendar on Outlook. Calendar (. ics file), import it into Outlook. Save a calendar as an . Outlook, clicking File > Save Calendar, and choosing the i. Calendar Format file type. Don’t have an Outlook. Learn how to create one at Outlook. Publish to a Web. DAV server If you have access to a web server that supports the World Wide Web Distributed Authoring and Versioning (Web. DAV) protocol, you can choose to publish calendars to that server instead. In your default calendar, on the Home tab, in the Share group, click Publish Online, and then click Publish to Web. DAV Server. For more information, see Publish your calendar on a Web. DAV server. Your Internet service provider (ISP) might provide features and tools to enable you to publish your calendar as a webpage. Contact your ISP to verify whether that feature is available to you. See also. Open another person's Exchange Calendar. Allow someone else to manage your mail and calendar. Installing an Exchange Server 2. Database Availability Group. The first article in this series on Exchange Server 2. Database Availability Groups provided an overview of Exchange 2. DAG concepts. In this article we'll go through the installation of a simple Exchange 2. DAG with two members. The DAG will have a MAPI network as well as one replication network. The file share witness will be another member server in the domain that has no Exchange 2. Preparing to Deploy an Exchange Server 2. Database Availability Group. Installing the Mailbox Servers. Database Availability Group members run the Mailbox server role. Although they can also run the Client Access server role this is separate and not required for DAG operations. In some situations the Client Access role should not be installed on the same server, for example: if you plan to use Network Load Balancing for Client Access server high availability (NLB is not supported to co- exist with the Failover Clustering that DAGs leverage)if you have any reason to believe you might later remove the Client Access server role (removal of a single server role is not possible in Exchange Server 2. Exchange Server 2. Windows Server 2. R2 and Windows Server 2. However, due to the dependency on Failover Clustering you should note the following requirements: Windows Server 2. R2 must be Enterprise edition to support Failover Clustering. Windows Server 2. Standard or Datacenter edition. To install your Exchange Server 2. DAG members: In my example scenario I have two servers E1. MB1 and E1. 5MB2 both running Windows Server 2. Each server is installed with both the Client Access and Mailbox server roles. A third server E1. FSW exists for the file share witness. Note: thanks to the concept of “incremental deployment” a DAG can be created using existing mailbox servers that are already in production with active mailboxes on them. There is no hard requirement to build brand new mailbox servers to be able to deploy a DAG. Configuring Permissions on the File Share Witness. Because the file share witness server is not an Exchange server some additional permissions are required. The Exchange Trusted Subsystem group in Active Directory must be added to the local Administrators group on the server. The file share witness also requires the File Server feature installed. PS C: \> Add- Windows. Feature FS- File. Server. 1PSC: \> Add- Windows. Feature FS- File. Server. And you should verify that File and Printer Sharing is allowed through the firewall. If the file share witness is another Exchange server, such as a Client Access server, it already has the correct permissions configured. For more information see: Configuring Networking for Exchange 2. Database Availability Groups. In this example each server is connected to the 1. The two Exchange servers are also connected to the 1. DAG replication traffic. Dedicated replication networks are not a requirement for Database Availability Groups, however if you do choose to deploy one or more replication networks you must ensure that DNS registration is disabled the network interfaces connected to those networks. The replication interfaces are also not configured with a default gateway. In the case where replication interfaces for the same replication network are on separate IP subnets, static routes are configured. However in this example that is not required. The configuration of the network interfaces is important for DAG network auto- config to be successful. For more information see Misconfigured Subnets Appear in Exchange Server 2. DAG Network. Configuring Existing Databases. In my example the server E1. MB1 and E1. 5MB2 had databases that were automatically created during Exchange 2. To prepare for database replication within the DAG I performed the following tasks: “Mailbox Database 1” on E1. MB1, which already contains active mailboxes, has been moved from the default folder path onto storage volumes dedicated to databases and transaction log files“Mailbox Database 2” on E1. MB2, which contained no mailboxes, has been removed from Exchange. Those steps may not be required in your environment depending on your existing databases. Pre- Staging the Cluster Name Object. Depending on your environment the pre- staging of the Cluster Name Object (CNO) may be required (it is a requirement if you are running Windows Server 2. DAG members), but in any case it is a recommended best practice. The CNO is simply a computer account object in Active Directory. There are two methods you can use to create the CNO. The first is to manually create the CNO using Active Directory Users & Computers. Create a new computer object with the name that you intend to give to your DAG. Then disable the computer account. Next, grant the computer account for the first DAG member Full Control permissions for the CNO computer account. Note that you may need to click the View menu in AD Users & Computers and enable Advanced Features before you can see the Security tab for the computer object. The other method for creating the CNO is to use Michel de Rooij's Cluster Name Object Pre- Staging script. Deploying an Exchange Server 2. Database Availability Group. Creating the Database Availability Group. In the Exchange Admin Center navigate to Servers - > Database Availability Groups and click the + icon to create a new DAG. Enter the following details for the new Database Availability Group: DAG name – this should match the CNO you pre- staged earlier. Witness server – this is required for all DAGs, even those that have an odd number of members and hence run in node majority quorum mode. Witness directory – this is optional. If you do not specify a directory Exchange will choose one for you. IP address – the DAG requires an IP address on each IP subnet that is part of the MAPI network. If you do not specify IP addresses the DAG will use DHCP instead. Click Save when you have entered all of the required details. Adding Database Availability Group Members. After the DAG has been created it still does not contain any actual members. These need to be added next. Highlight the new Database Availability Group and click the icon to manage DAG membership. Add the servers that you wish to join the DAG and then click Save. This process will install and configure the Failover Clustering feature of Windows Server 2. DAG members to the cluster. Note: if you're using a non- Exchange server for the file share witness, and you have correctly configured the permissions on the FSW, you will still see a warning at this stage that the Exchange Trusted Subsystem is not a member of the local administrators group on the FSW. This is a bug that can be disregarded. When the operation is complete the Database Availability Group will display the members you added. In the next part of this series we will look at configuring the database copies in the DAG.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |