After renovation

We have been waiting to start our life on this little wonderful place that we call home, but the monetary crisis h

By Unknown with No comments

Disewakan Rumah Maleo Bintaro IX tanpa perantara

Rumah dua tingkat
3 kamar tidur
2 kamar Mandi
1 kamar pembantu + kamar mandi
garasi untuk 2 mobil
Listrik 2200 watt

Lokasi sangat asri di Maleo Bintaro sektor 9
Untuk keterangan lebih lanjut hubungi no telepon 021-93080062

By Unknown with No comments

Just drive me home

My lovely wife and I

By Unknown with No comments

Exchange 2007 Moving Mailboxes

When you move a mailbox, you move the data in the mailbox from one mailbox database to another. Be aware of the following when using Move-Mailbox:

• You can move a mailbox to a different database on the same server, to a different server within the same forest, or to a different server in another forest. (To move a mailbox from one forest to another, you must use the Move-Mailbox cmdlet.)
• You can move mailboxes from Exchange 2000/2003 servers to Exchange 2007, or from Exchange 2007 to Exchange 2000/2003.
• To move a mailbox, the account you use must be delegated as the Exchange Recipient Administrator role and the Account Operator role for the applicable Active Directory containers.
• By default, when you move a mailbox the source mailbox data is not deleted. Use -SourceMailboxCleanupOptions DeleteSourceMailbox to delete the source mailbox after the move.
• Only one instance of the Move Mailbox wizard can be run at a time from the Exchange Management Console. You can, however, run multiple instances of the Exchange Management Console and run an instance of the Move Mailbox Wizard from each.
• The move will fail if the size limit on the source mailbox exceeds the size limit of the target database. Use -MailboxSizeLimitOptions PreserveSource to set the mailbox size limit for the source mailbox on the target mailbox.
• Use the -PreserveMailboxSizeLimit switch to keep the current user mailbox settings when moving a mailbox.
• Move-Mailbox does not change the user account association. You cannot use Move-Mailbox to move the mailbox from one user to another.
• When moving mailboxes from Exchange 2007 to Exchange 2003, you might run into cases where the user rule size on the mailbox exceeds the maximum size limit for user rules on Exchange 2003 (Exchange 2007 supports 64 KB for rules, while Exchange 2003 only supports 32 KB). If the 2007 mailbox has rules larger than 32 KB, use the -IgnoreRuleLimitErrors switch to not move the rules.

While the Move-Mailbox cmdlet is useful, it does have its limitations. The following table describes the processes used to move and merge mailboxes for various situations:

Action	Description
Move a single mailbox within a forest	Use the Move Mailbox wizard or the Move-Mailbox cmdlet to move a mailbox and its contents from one mailbox database to another.
Move a mailbox across forests	You can use Move-Mailbox to move mailboxes across forests. Use the following process: Move the user account from the source forest to the target forest using the Active Directory Migration Tool (ADMT) version 3.0. Run $SourceCredential = Get-Credential to create a credential object that contains account information for the source forest. Run $TargetCredential = Get-Credential to create a credential object that contains account information for the target forest. Run the Move-Mailbox cmdlet to move the mailbox. In addition to the target database and the mailbox identity, you will need to supply the following: -SourceForestCredential $SourceCredential -TargetForestCredential $TargetCredential Either the -GlobalCatalog switch (to identify a target global catalog server) or the -SourceForestGlobalCatalog switch. The -NTAccountOU to identify the location of the user account. When moving mailboxes across forests, be aware of the following: You must have the Exchange Recipient Administrator role for the Exchange organization and the Exchange Server Administrator role and local Administrators group for both the source and target forests and servers. You must have a domain controller running Windows Server 2003 in both the source and target domains. You can move from Exchange 2000/2003 to Exchange 2007, or from Exchange 2003 to Exchange 2007 across forests. You cannot move mailboxes from Exchange 2007 to Exchange 2000 across forests. Use -SourceMailboxCleanupOptions DeleteSourceNTAccount to delete the source user account and mailboxes if all three of the following are true: You are moving a user's mailbox to a new forest. You have already moved the user account to the new forest using the ADMT. You want to delete both the source mailbox and the source user account after the mailbox is moved.
Move an entire mailbox database on the same server	If you need to move an entire mailbox database and all of its mailboxes to a different location on the same server, use the following process: If necessary, run Move-StorageGroupPath or the console wizard to move the log files. Run Move-DatabasePath or the console wizard to move the database file. Run Move-Mailbox with the -ConfigurationOnly switch to change the configuration information in Active Directory so that the mailboxes all point to the new location of the database.
Move an entire mailbox database to a different server	If you need to move an entire mailbox database and all of its mailboxes to a different server, use the following process: Commit any uncommitted log files to the database. Use Get-StorageGroup myServer\myStorageGroup | fl LogfilePrefix to identify the log file prefix number. At a command prompt, run ESEUTIL /R prefix. Create the database on the target server. Set the This database can be over written by restore attribute on the target database using the console or run Set-MailboxDatabase with the -AllowFileResore switch. Copy the database files from the source server to the target server in the same location as the target server database files. Mount the target database. Run Move-Mailbox with the -ConfigurationOnly switch to change the configuration information in Active Directory so that the mailboxes all point to the new location of the database. Mailbox databases can only be moved between Exchange 2007 servers in the same Exchange organization.
Merge mailboxes across forests	When you move mailboxes across forests, the user mailbox might be unavailable for a time. To move mailboxes with minimal interruption of mail service, use the following process: Run Move-Mailbox to move the mailbox to the target forest. Do not delete the user account or the mailbox. Run ADMT to migrate the user account to the target forest. Disable access to the source mailbox. This causes the user account to use the mailbox in the target forest. Run Move-Mailbox with the -AllowMerge switch to merge the source mailbox with the target mailbox. Only messages that were sent or received during the transition will be merged into the target mailbox. Manually delete the user account and the mailbox in the source forest.
Move a mailbox to a different user	When you use the Move-Mailbox cmdlet, the mailbox is moved to a different location but is still associated with the same user account. If you have a mailbox for one user that you want to associate with another user: Run Disable-Mailbox to unlink the mailbox from the source user account or Remove-Mailbox to delete the user account. Run Connect-Mailbox to mail-enable the target user account and link the mailbox to the user. Note: You cannot connect a mailbox to a user that already has a mailbox. The target user account must not be mail-enabled, and must be in the same forest as the disconnected mailbox.
Export mailbox data to another mailbox	If you want to move mailbox data to a different user who already has a mailbox, you will need to export the mailbox contents from the source mailbox and import it into the target mailbox. Run the Export-Mailbox cmdlet to export and import the data in a single step. All data in the source mailbox is copied into a folder in the destination mailbox. You can export data from connected and disconnected mailboxes. The source mailbox and its data are not deleted. If connected, the source mailbox remains connected. You can only export mailbox data within a forest. With Exchange 2007 SP1, you can also export data to a .pst file. You can then use the Import-Mailbox cmdlet to import the .pst file into a mailbox.
Restore mailbox data	If a disconnected mailbox no longer exists, you can move mailbox data to the same or another mailbox by restoring the mailbox. To recover a lost mailbox: Create a recovery storage group. Create a mailbox database in the recovery storage group. Set the This database can be over written by restore attribute on the target database using the console or run Set-MailboxDatabase with the -AllowFileResore switch. Restore the mailbox database to the recovery database. Mount the recovery database. Run Restore-Mailbox to restore a mailbox from the recovery database to a target mailbox. When restoring data, be aware of the following: You can restore data from one mailbox to the same mailbox or to a different mailbox. You can only restore data to a mailbox in the same Exchange organization. When restoring to the same mailbox, you can either merge data into the existing mailbox, or copy all data into a target directory. Use the -TargetFolder switch to identify the target directory. Restored data does not overwrite existing data. When restoring to a different mailbox, you must include the -TargetFolder switch.

By Unknown with No comments

Exchange 2007 Resource Scheduling Facts

For Room and Equipment mailboxes, you can configure automatic scheduling so that meeting requests sent to the resource mailbox are processed automatically. There are two methods to enable automatic scheduling:

• With Calendar Attendant scheduling, the Calendar Attendant is responsible for granting scheduling requests based on the resource calendar.
• With booking policies, you define policies that identify who can schedule resources, when the resource can be scheduled, and the message that users receive in response to a booking request.

You cannot use the Management Console to configure resource scheduling. Use the Set-MailboxCalendarSettings cmdlet to enable and configure scheduling requests. The following table describes various resource scheduling tasks:

Task	Description
Configure automatic booking	To configure automatic booking, you must enable the booking type. Use the -AutomateProcessing switch to enable or disable automatic scheduling on the mailbox. The None parameter disables resource scheduling. The AutoUpdate parameter enables resource scheduling using the Calendar Attendant. The AutoAccept parameter enables scheduling using resource booking policies that you define.
Identify resource delegates	A resource delegate is a user assigned to the resource that approves or rejects meeting requests that are not processed automatically. For example, the delegate approves requests that do not meet the defined policies. Use the -ResourceDelegates switch to identify one or more users who are resource delegates.
Identify who can schedule a resource	When you enable resource booking, you manually identify who can submit meeting requests. Use the following switches to enable booking submissions from all users: When -AllBookInPolicy is set to $true, all users can submit scheduling requests. Requests that meet the defined policies are approved (booked) automatically. When -AllRequestInPolicy is set to $true, all users submit scheduling requests. Requests that meet the policy conditions are sent to the resource delegate for approval. When -AllRequestOutOfPolicy is set to $true, users can submit requests that do not meet policy conditions. These requests must be approved by a resource delegate. Use the following switches to identify a list of users who are allowed to submit scheduling requests: Use -BookInPolicy to identify a list of users whose requests are granted automatically as long as those requests meet the policy conditions. Use -RequestInPolicy to identify a list of users who can submit requests, but whose requests must be approved by the resource delegate. Use -RequestOutOfPolicy to identify a list of users who can submit requests that do not meet policy conditions. Requests must be approved by a resource delegate.
Configure policy settings	When using resource booking, use the following switches to configure when the resource can be scheduled: Use -ScheduleOnlyDuringWorkingHours to limit scheduling during normal work times. Use -AllowRecurringMeetings to allow or disable scheduling requests that occur on a regular basis. Use -BookingWindowInDays to require that booking requests be made the specified number of days before the scheduled time. Use -AllowConflicts to allow the resource booking agent to grant requests that conflict.

Additional command switches allow you to configure the response sent to meeting organizers, remove attachments or comments from the calendar entries, or delete non-calendar requests.
Note: To run the Set-MailboxCalendarSettings cmdlet, users must have the Exchange Organization Administrator role. This is because settings affect not only the recipient, but also organizational-wide settings.

By Unknown with No comments

Exchange 2007 Recipient Facts

A recipient is an Active Directory object that has Exchange mail capabilities. The following table explains the Exchange 2007 recipient types:

Recipient type	Description
User mailbox	A user mailbox is associated with an Active Directory user account. All of the messages, calendar items, documents, contacts, tasks, and other data that are associated with a mailbox-enabled user are hosted on one of the mailbox servers within an Exchange organization. A mailbox-enabled user can log on to the domain and access resources on the network according to the permissions and groups to which they are assigned. User mailboxes are the most common type of Exchange recipient. Note: The mailbox data that is stored in the Exchange mailbox database is marked for deletion and the associated user account is also deleted from Active Directory when a mailbox is removed. The user account can be retained by disabling the mailbox.
Mail user	A mail user is a mail-enabled Active Directory user that has an e-mail address associated with an account, but whose mailbox is stored on an external mail system. For example, a contractor who is working for the organization but is using their own e-mail address.
Mail contact	A mail contact is a mail-enabled Active Directory contact that contains information about people or organizations that exist outside an Exchange organization. Mail contacts are used to make it easier for users within an organization to locate the contact details of people outside of the organization. A mail contact is similar to a mail user, but a contact can't be used for logon.
Mail-enabled universal distribution group	A universal distribution group is a mail-enabled Active Directory distribution group object that is used to distribute e-mail messages to a large number of people in an organization, such as entire departments or groups. Note: Unlike previous versions of Exchange, a distribution group in Exchange 2007 must be a universal group.
Mail-enabled universal security group	A universal security group is a mail-enabled Active Directory security group object used to grant access permissions to resources in Active Directory in addition to distributing messages to departments or groups. Use a security group if you need to use the group to control access to resources in addition to using it for mail distribution.
Dynamic distribution group	A dynamic distribution group is a distribution group whose membership is defined by the results of a query (as opposed to a defined set of recipients) which is executed every time a message is sent to the group. This is optimal for environments in which people move groups or buildings often and e-mail groups need to be able to accommodate changes as they occur. Note: Because of the additional load that is placed on global catalog servers when a dynamic distribution group query is run, it is best to limit the amount of dynamic distribution groups that are created.
Mail-enabled non-universal group	A non-universal group is a mail-enabled Active Directory global or local group object which has been brought over from previous versions of Exchange. You can manage these groups with Exchange 2007, but not create them.
Room mailbox	A room mailbox is assigned to a meeting location. Use room mailboxes to schedule meeting rooms. When you create a room mailbox, a disabled user account is created for the room. You then specify a user who manages the room, or you can configure a calendar so schedule requests are handled automatically.
Equipment mailbox	An equipment mailbox is assigned to a resource that does not have a specific location. Examples include a portable projector or a company car. You can use equipment mailboxes for requesting and scheduling equipment use. Like a room mailbox, an equipment mailbox has a disabled user account and a managing user. You can also configure the calendar for automatic scheduling.
Mail-enabled public folder	A mail-enabled public folder is a public folder that can receive messages. Messages that are sent to e-mail addresses are posted in public folders.
Linked mailbox	A linked mailbox is a mailbox that is assigned to an individual user in a separate, trusted forest. Multiple forests usually exist for the following reasons: An organization deploys one forest for user accounts for the staff and deploys a second forest for the resources for the organization such a print services or Exchange. Administration requirements are distinct for different parts of the organization. Different areas of the organization require distinct schemas. Multiple companies have merged together. You should understand the following about linked mailboxes: When a linked mailbox is created, a mailbox and a disabled user account are created in the forest which hosts the Exchange organization. Once the mailbox has been created, it is then linked or associated with a user account that resides in the second forest. To assign an account from the second forest to the mailbox, a trust relationship must exist between the domain that contains the Exchange server and the domain in which the user account resides.
Shared mailbox	A shared mailbox performs the same functions as a user mailbox, but is associated with multiple Active Directory user accounts. Note: Even though Exchange 2007 supports shared mailboxes, it is a de-emphasized feature that can only be managed through the Exchange Management Shell. It is recommended to use resource mailboxes or Microsoft SharePoint Portal Server portals for collaboration instead of shared mailboxes.
Legacy mailbox	A legacy mailbox is a mailbox which resides on an Exchange Server 2003 or Exchange 2000 Server.
Mail forest contact	A mail forest contact is a read-only recipient object from another forest that is created and managed by Microsoft Identity Integration Server (MIIS) synchronization. Mail forest contacts cannot be removed or modified through the Exchange Management Console or the Exchange Management Shell.
Microsoft Exchange recipient	The Microsoft Exchange recipient is a special recipient object that: Differentiates system-generated messages from other messages. Replaces the “System Administrator” sender that was used for system-generated messages in earlier versions of Microsoft Exchange Server.

By Unknown with No comments

Exchange 2007 Server Preparation

Before installing Exchange Server 2007, you must first evaluate the type of hardware that is available. The hardware and directory requirements of Exchange 2007 are outlined in the following table:

Component	Description
Architecture	Exchange Server 2007 supports only 64-bit processors in a production environment. This change increases the total amount of memory that can be used by Exchange. Supported processors are: Intel processors that support Intel Extended Memory 64 Technology (for example Intel Xeon or Intel Opteron processors). AMD processors that support AMD64 (for example AMD Athlon processors). You should be aware of the following information concerning processors: You must choose a processor that works with the x64-based version of Windows Server 2003. Because Intel Itanium processors cannot be used with x64-based versions of Windows Server 2003, they cannot be used with Exchange 2007. Exchange Server 2007 shows significant performance benefits when employing dual-core processors. A 32-bit version of Exchange is available, but is only supported in testing and training environments. Management tools can be installed on 32-bit processors in production environments. To do this, you must download the 32-bit version of Exchange 2007.
Operating system	You can install Exchange Server 2007 on the following operating systems: x64-bit Windows Server 2003 SP1 or later. 64-bit versions of Windows Server 2008 is supported beginning with Exchange 2007 SP1. 32-bit versions of Windows Server 2003 are supported only in testing and training environments (and only with the 32-bit version of Exchange).
RAM	The minimum RAM requirement to support Exchange 2007 is 2 GB per server. Depending upon the server role being installed, the recommended RAM is: Edge Transport server: 2 GB minimum or 1 GB per core (whichever is higher), with a maximum of 16 GB per server. Hub Transport server: 2 GB minimum or 1 GB per core (whichever is higher), with a maximum of 16 GB per server. Client Access server: 2 GB minimum or 1 GB per core (whichever is higher), with a maximum of 8 GB per server. Unified Messaging server: 2 GB minimum or 1 GB per core (whichever is higher), with a maximum of 4 GB per server. Mailbox server: Recommended 2 GB minimum, with an additional 2-5 MB per mailbox, with a maximum of 32 GB per server. Multi Role (Hub, CAS, UM, Mailbox): Recommended 4 GB minimum, with an additional 2-5 MB per mailbox, with a maximum of 8-32 GB per server (depending on the combination of roles installed). You should know the following about selecting memory for your Exchange 2007 server: 32 GB is not a physical limitation; rather, it is currently the most cost-efficient memory configuration. The major advantage of having large amounts of RAM on a server is that it significantly lessens the workload of the disk subsystem. The disadvantage of implementing larger RAM is the cost of the RAM and installation is high compared to the amount of performance gained. Depending on the system, you might need to choose slower memory in order to get up to the maximum supported memory. Installing more memory might require using slower RAM.
Free disk space	An Exchange Server 2007 installation requires: At least 1.2 GB of available disk space for the installation. 200 MB of available disk space on the system drive. An additional 500 MB of disk space for each Unified Messaging (UM) language pack you install. On Hub Transport and Edge Transport servers, 4 GB of space for message queues. (This requirement has been reduced to 500 MB on Exchange 2007 SP1.)
File System	To install Exchange 2007, the following disk partitions should be formatted as NTFS: System partition Partitions containing database files   Partitions that store Exchange binary files Partitions containing storage group files, including transaction log files Partitions containing other Exchange files
Disk subsystem	The disk subsystem must have enough storage capacity to support the I/O operations of the server and also support the amount of mailbox space allotted to each user. Exchange server 2007 supports: Locally-attached storage Storage Area Networks (implementation of Fibre Channel technology is ideal) IP SCSI Network-Attached Storage technology. Be aware of the following when designing disk use for Exchange 2007: Although you can install Exchange 2007 on a single disk, for maximum performance you should use different disks for system files, database files, and transaction log files. Because of the increase in RAM in Exchange 2007, you can have a smaller number of large disks without seeing a decrease in performance.
Additional requirements	A system must meet the following additional requirements to install Exchange 2007: A local- or network-accessible DVD-ROM drive. Screen resolution set to 800 x 600 pixels or higher.

Before installing Exchange 2007, the following components are required for all server roles:

• .NET Framework 2.0
• PowerShell 1.0
• Microsoft Management Console 3.0
• All necessary hotfixes

Note: If you use the Setup wizard in the graphical installation, these components (except for the hotfixes) will be added automatically.
Once the common criteria is in place, you must install the individual required components of whichever server roles you install:

Role	Additional Components
Mailbox server	A Mailbox server requires the following components: Internet Information Services (IIS) Enable network COM+ access in IIS World Wide Web Publishing Service (W3SVC)
Unified messaging server	A Unified Messaging server requires the installation of: The Microsoft Speech Engine service The Windows Media Audio Voice Codec The Windows Media Encoder Microsoft Core XML Services (MSXML) Version 6.0
Client Access server	The Client Access server requires: World Wide Web Publishing Service (W3SVC) RPC/HTTP proxy Windows networking component on any computer that provides Microsoft Outlook Anywhere access (recommended one per site) ASP.NET version 2.0 Distributed Transaction Coordinator Service
Edge Transport server	An Edge Transport server requires the Active Directory Application Mode (ADAM) to be installed before the Edge Transport server can be installed. It is best to accept all of the default settings during the ADAM installation. Note: If you are installing Exchange 2007 SP1, install Active Directory Lightweight Directory Services (AD LDS) instead.

Note: When installing an Exchange server role in Exchange 2007, it is not necessary to install the SMTP or the NNTP components before installation is initiated, as was the case in Exchange 2003. If you install the Hub Transport server role or the Edge Transport server role on a machine, it cannot have the SMTP service or the NNTP services installed on it. In addition, the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol must not be installed on any Exchange server.
Client computers or mobile devices must have the following installed to run certain applications:

Application	Additional Components
Outlook	To use Microsoft Outlook to access an Exchange 2007 mailbox, you must have one of the following versions of Outlook installed on the client's computer: Outlook 2002 Outlook 2003 Office Outlook 2007
Outlook Web Access	The client computer must have a Web browser installed. Microsoft Internet Explorer must be installed if Integrated Windows authentication is employed.
Mailbox access for mobile devices	For mobile devices access to mailboxes requires the following: Windows Mobile 2003 Second Edition Windows Mobile 5.0 with the Messaging and Security Feature Pack (MSFP) A non-Windows operating system that are compatible with Exchange ActiveSync

By Unknown with No comments