i-away

Earlier today the Exchange CXP team released an updated version of Update Rollup 4 for Exchange Server 2010 SP1 to the Download Center. This updated release is being made available after a complete review and revalidation of the list of fixes included in the previously released version of Rollup 4 dated June 22, 2011. The review completed by the Exchange CXP team determined that the issue identified in 'KB 2581545: The copy or move operation on a folder that contains subfolders does not work as expected after you install Update Rollup 4 for Exchange Server 2010 SP1 dated June 22, 2011’ introduced a serious regression in the original release of Rollup 4. As a result, a new version of Rollup 4 dated July 23, 2011 has been tested and released with the change that caused the regression removed. The re-release of Rollup 4 is tracked by 'KB 2579150: Description of Update Rollup 4 for Exchange Server 2010 Service Pack 1'. The updated Rollup 4 is being released to allow customers to install the list of fixes previously committed to on the normal rollup schedule using normal rollup installation routines without the need for further action. The re-released version of Rollup 4 is functionally equivalent to the combination of the original Rollup 4 release and (the interim updatein) KB 2581545. Here are answers to some install questions: Customers who have installed KB 2509910 (Rollup 4, dated June 22, 2011) and KB2581545 (fix for Rollup 4 regression) do not need to install KB 2579150 (re-released Rollup 4) but may do so if they choose to. Customers who have already installed KB 2581545 and want to update their systems to the updated Rollup 4 should first uninstall KB 2581545 (or any interim updates) prior to installing the new rollup. You do not need to uninstall original RU4 (KB 2509910) to install the re-released RU4 package (KB2579150). The re-release of Rollup 4 does not change the release plans for Update Rollup 5 for Exchange Server 2010 Service Pack 1. Rollup 5 is currently scheduled to release in August 2011. Some of the above KnowledgeBase articles are not replicated/live at the time of writing this post. Please check back later in the day if you can't reach them. General Notes Note for Exchange 2010 Customers using the Arabic and Hebrew language version: We introduced two new languages with the release of Service Pack 1, Arabic and Hebrew. At present we are working through the process of modifying our installers to incorporate these two languages. Customers running either of the two language versions affected are advised to download and install the English language version of the rollup which contains all of the same fixes. Note for Forefront users: For those of you running Forefront Security for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup's installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.

he Exchange Sustained Engineering team recently made the decision to recall the June 22, 2011 release of Exchange 2010 SP1 Rollup 4. This was not an action we took lightly and we understand how disruptive this was to customers. We would like to provide you with some details that will give you a deeper understanding of what actually happened and, more importantly, what improvements we are making to prevent this in the future. Q: What actually triggered the recall? A: While fixing a bug that prevented deleted public folders from being recovered, we exposed an untested set of conditions with the Outlook client. When moving or copying a folder, Outlook passes a flag on a remote procedure call that instructs the Information Store to open deleted items which haven’t been purged. Our fix inadvertently caused the RPC to skip all content that wasn’t marked for deletion because we were not expecting this flag on the call from Outlook on the copy and move operations. Q: Why didn’t you test this scenario? A: The short answer is we thought we did. We didn’t realize we missed a key interaction between Exchange and Outlook. The Exchange team has well over 100,000 automated tests that we use to validate our product before we ship it. With the richness and number of scenarios and behaviors that Exchange supports, automated testing is the only scalable solution. We execute these tests in varying scenarios and conditions repeatedly before we release the software to our customers. We also supplement these tests with manual validation where necessary. The downside of our tests is that they primarily exercise the interfaces we expose and are designed around our specifications. They do test positive and negative conditions to catch unexpected behavior and we did execute numerous folder copy and move tests against the modified code which all passed. What we did not realize is that our tests were not emulating the procedure call as executed by Outlook. Q: Exchange has been around a while, why did this happen now? A: In Exchange 2010 we introduced a feature called RPC Client Access. This functionality is responsible for serving as the MAPI endpoint for Outlook clients. It allowed us to abstract client connections away from the Information Store (on Mailbox servers) and cause all Outlook clients to connect to the RPC Client Access service. As part of our investigation, we discovered that there was some specific code added to the Exchange 2003 Information Store to handle the procedure call from Outlook using the extra flag. This code was also carried forward into Exchange 2007. But when the Exchange team added the RPC Client Access service to Exchange 2010, that code was not incorporated into the RPC Client Access service because it was mistakenly believed to be legacy Outlook behavior that was no longer required. That, unfortunately, turned out not to be the case. The fact that we were not allowing a deleted public folder to be recovered was masking this new bug completely. Q: Are there other similar issues lurking in RPC Client Access? A: We do not believe so. The RPC Client Access functionality has been well-tested at scale and proven to be reliable for the millions of mailboxes hosted in on-premises deployment and in our own Office 365 and Live@EDU services. Q: What are you doing to prevent similar things from happening in the future? A: We have conducted a top-to-bottom review of the process we use to triage, develop and validate changes for Rollups and Service Packs and are making several improvements. We have changed the way we evaluate a customer requested fix to ensure that we more accurately identify the risk and usage scenarios that must be validated for a given fix. Recognizing the diversity of clients used to connect to Exchange, we are increasing our client driven test coverage to broaden the usage patterns validated prior to release. Most notably, we are working even closer with our counterparts in Outlook to use their automated test coverage against each of our releases as well. We are also looking to increase coverage for other clients as well.

Struggling to find an overview of how what the latest EAS features are? Planning your migration from Exchange 2003 and looking for a basic introduction to Database Availability Groups? These videos are for you! The Microsoft Exchange team has produced a new portfolio of videos designed to give customers a fundamental technical education on Exchange Server 2010. There are currently seven videos in the series covering the following topics: Archiving and Discovery Mailbox Resiliency Management Mobility Outlook and Exchange Outlook Web App Unified Messaging The objective of the video series is to provide an introductory curriculum for IT professionals to learn more about the benefits of Exchange Server 2010. While TechNet provides great technical documentation at a more granular level, this video series should help bridge the gap for those who are new to Exchange 2010 and still trying to learn about the technical fundamentals of the product. Each video runs 20-30 minutes long and includes an overview of the workload as well as a technical demonstration of 3-4 core scenarios related to that workload. The “Exchange Server 2010 Technical Video Series” is hosted by Ann Vu and presented by subject matter experts from the Microsoft Exchange team. You can find these videos on the front page of Exchange Server TechCenter on TechNet. Please help us evangelize these videos to anyone who wants to learn more about Exchange Server 2010 and let us know your thoughts. As always, your feedback is extremely valuable to us. Many thanks in advance! Source:Steven Chew

Βασίλη νομίζω ότι ακολουθώντας αυτό θα λυθεί το πρόβλημα σου . Επίσης απο το log του 2003 έχω μια υποψία ότι δεν φορτώνονται σωστά τα smtp verbs. Φυσιολογικά η σειρά είναι: 250-mail1.example.com Hello [172.16.0.1] 250-TURN 250-ATRN 250-SIZE 5242880 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250-X-EXPS GSSAPI NTLM * 250-AUTH GSSAPI NTLM 240-X-EXPS=LOGIN * 250-X-LINK2STATE * 250-XEXCH50 * 250 OK Αν δεν το βλέπεις αυτό σημαίνει ότι έχεις αλλού πρόβλημα. Επίσης βλέπω ότι δεν φορτώνει το TLS πριν το κάνει start. Έλεγξε το και πες μας.

We’ve been sharing updates on Windows Thin PC (WinTPC) for some time now and are excited to announce that today WinTPC reached its RTM milestone and will become generally available for download on July 1, 2011. As we’ve been talking about, customers told us that they want an easy way to repurpose their existing PCs as thin clients. WinTPC makes this a reality and plays a part in our broader desktop virtualization strategy , which is to deliver the flexibility to work from everywhere, improve compliance and business continuity, and simplify management so that IT professionals can deliver better service to employees. With the above goal in mind we created WinTPC to help customers repurpose their PCs as thin clients, thereby driving down the cost of VDI. We used additional feedback gathered from customers in our Community Technology Preview (CTP) to add a few features in the RTM. Keyboard Filter: WinTPC will have the capability to allow customers to lock certain key combinations, such as Ctrl +Alt + Delete, from being utilized and taking effect on a Windows Thin PC device, thereby providing customers with greater level of security and control over user interaction with their WinTPCs. International IMEs (Input Method Editor) support: WinTPC will now include the option to support international keyboards. Key Management Server (KMS)/Multiple Activation Key (MAK): WinTPC will now be able to activate against a customer’s existing KMS server or use MAK keys, which enables quick and easy activation mechanisms that customers already use for their Windows desktops today. Ultimately, the goal with the final version of WinTPC is to enable customers to extend existing investments in hardware and software for their VDI environments, so that, where appropriate, thin client computing becomes a natural part of their overall desktop strategy. And there is demand in the industry for this capability, according to recent survey published by Gartner nearly 60% of respondents indicated that they are interested in reconfiguring existing PCs as thin clients when asked “Is your organization planning to use existing clients/PCs for HVD, or will they purchase new client hardware?” (Source: Gartner, Survey Analysis: 2010 Data Center Conference, x86 Virtualization and Hosted Virtual Desktops Driven by Business Agility, Not by Cost Savings. February 2011, Note: Number of respondents equals 182 - multiple responses allowed). With the customer feedback through our CTP, we also had the opportunity to work with a few customers to test WinTPC and put it through the paces. One was Deluxe Corporation, a $1.4 billion financial services company with locations in the United States, Canada and Ireland, who worked closely with us during product development. Deluxe is known as a dynamic organization that combines innovation with integrity and found that WinTPC was exactly what they were looking for. We talked with Scott Valeri, Manager of Enterprise Desktop & Mobile Architecture & Engineering at Deluxe who said, "WinTPC is a strategic tool within our desktop deployment model and is the next natural step in our thin client computing strategy, as we evaluate ways to providing a rich Windows experience from both fixed and mobile thin PCs. WinTPC enables [us] to leverage existing investments in PCs as well as new investments in Thin PCs equipped with Atom CPUs. As Deluxe Corporation migrates additional users to virtual desktops, WinTPC will be the primary operating system used to reach virtual desktops." In addition to Deluxe Corporation, we also received feedback from other customers. We have tried to answer a lot of your questions through the WinTPC site, but would like to touch upon a few frequently asked questions that have come up over the course of the beta program. Q: Will WinTPC be supported by Forefront Endpoint Protection (FEP)? A: Another key piece of feedback we received from customers is the need for Forefront Endpoint Protection (FEP) support for WinTPC. Today, I am happy to announce that FEP support will be coming to WinTPC in Q3 CY2011, which is in the same quarter as the GA for WinTPC. Customers will be able to extend their investments with FEP to WinTPC, unifying their anti-malware strategy across PCs and WinTPCs. Q: Will customers be able to run applications on WinTPC? A: WinTPC is designed to be a thin client device, and therefore only applications that fall into the certain categories are enabled. These categories include security, management, terminal emulation, Remote Desktop and similar technologies, web browsers, media players, instant messaging clients, document viewers, NET Framework and Java Virtual Machine. If customers want to locally run productivity applications such as Microsoft Office, or any other application that does not fall into the categories mentioned above, they would be better off using a PC, as thin client computing may not be the best fit for their scenarios. Q: How can I extend my management to WinTPC? A: Management is a critical component of any desktop virtualization strategy and you should be able to leverage existing infrastructure wherever you can to reduce complexity and we believe this holds true for the access device as well. WinTPC can be managed using your existing System Center Configuration Manager deployment, thereby ensuring that you are able to leverage existing investments in technology, processes and expertise. Additionally, the new Windows Embedded Device Manager 2011 helps simplify management of devices where write filters are turned on. Q: Will I be able to use Citrix Receiver with WinTPC? A: As discussed in previous posts, Microsoft and Citrix work closely together to bring you a complete desktop virtualization solution and WinTPC is no different. We are happy to let you know that our partnership is here for you once again and we’ve made sure the WinTPC and Citrix’s Receiver technology work together, so if you’re accessing XenApp or Xendesktop via WinTPC you’ll have a great experience! We want to say thank you to everyone for the interest in WinTPC over the past few months – we value the feedback and encourage you to continue giving us your thoughts in the comment section below. For more information, check out the WinTPC site. Also, if you didn’t enroll in the beta program but can’t wait until it becomes generally available to try it out, no need to worry. You can still register and download the beta software from http://connect.micrsoft.com until July 1.v Source. Ps: Future Forecast : Thin Weather and Clouds...Stay Tuned!

Βασίλη καλησπέρα, Πληροφορίες και οδηγίες θα βρείς εδώ διαβασε προσεκτικά καθώς η διαδικασία αλλάζει ανάλογα με την έκδοση του Exchange.

Recently, some customers reported that when they create a DAG, they get a warning message that states the following: The Exchange Trusted Subsystem is not a member of the local Administrators group on specified witness server <ServerName>. In these cases, the customer’s intended witness server was not an Exchange 2010 server. As documented in TechNet, if the witness server you specify isn't an Exchange 2010 server, you must add the Exchange Trusted Subsystem (ETS) universal security group (USG) to the local Administrators group on the witness server. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed. After some inspection, the customers confirmed that, contrary to the error message, the ETS USG was a member of the local administrators group on their intended witness server. Moreover, even though this warning appeared, there were no ill effects in functionality. The directory and share on the witness server were created as needed, the file share witness cluster resource was online, and the DAG passed all replication health checks. After hearing about this, I went to my lab to test this, and I was able to reproduce the issue. I added the ETS USG to the local administrators group on my witness server (a Windows 2008 file server) and ran New-DatabaseAvailabilityGroup, specifying my witness server. I received the same warning message, and verified that despite the message, all was perfectly healthy with the DAG, and there were no permission problems, witness server or cluster problems or other issues. Even though it appeared as though this warning message could be safely ignored, I wondered why we were getting it in the first place. So I went digging into the source code to find out. Let me describe what is happening and why you, too, can safely ignore the warning message. During various DAG-related tasks that configure witness server properties (namely, New-DatabaseAvailabilityGroup, Set-DatabaseAvailabilityGroup and Restore-DatabaseAvailabilityGroup), the code is actually checking to see if the witness server is a member of the Exchange Trusted Subsystem USG. As you may know, there is no requirement that the witness server be a member of the ETS USG. Nonetheless, the code for these tasks does check for this, and if it finds that the witness server is not a member of the ETS USG, it issues a warning message. Unfortunately, to confuse things even more, the warning message says: The Exchange Trusted Subsystem is not a member of the local Administrators group on specified witness server <ServerName>. It says nothing about the witness server not being a member of the ETS USG, even though the code is checking for that. Instead, it makes it appear as though the permission perquisites have not been satisfied, even though they actually have. But, even though the message does not pertain to the actual check that failed, that does not make this a string bug. This is a code bug, as there is no requirement that the witness server be a member of the ETS USG. Thus, the code should not be checking for this condition. If this bug is fixed and the check is removed, the string will be removed with it. Unless and until that happens, if you are seeing this warning message when you are using any of the above-mentioned tasks, and you have verified that the ETS USG is a member of the local administrators group on your witness server, then you can likely safely ignore the warning message. You should run Test-ReplicationHealth to verify the health of the DAG once members have been added to it. Because we are doing this check in code, you can of course add the witness server to the ETS group, and also make the ETS group a member of the local administrators group on the witness server, and all of these tasks will complete without this warning message. But, don't do that in production because (1) it is not needed and (2) it gives the witness server way more permissions than it should ever have (unless of course, the witness server is an Exchange 2010 server).

Στο προηγούμενο post μας είχαμε εγκαταστήσει 2 CAS + Mailbox Server και 2 Hub Transport Server. Στο post αυτό θα παραμετροποιήσουμε τα Database Availability Groups μεταξύ των 2 Mailbox servers. Όπως είναι γνωστό θα πρέπει να έχει εγκατασταθεί το Failover Cluster feature απο τον Server Manager. Επίσης θα πρέπει να επιλέξουμε 1 Witness server ( προτείνεται κάποιος Hub Transport ) και αν θέλουμε και 1 Alternate Witness Server. Με την βοήθεια του Powershell λοιπόν: Αφού δημιουργήσαμε το DAG ας προσθέσουμε τον 1ο server: Get-DatabaseAvailabilityGroup | FL Name,*IP* Name : ConotosoDAG DatabaseAvailabilityGroupIpv4Addresses : {} DatabaseAvailabilityGroupIpAddresses : {} Το DAG χρειάζεται 2 διαφορετικά network 1 Public και 1 για το μεταξύ τους Replication. Public Network: 178.65.32.36/24 Replication Network: 192.168.0.0/16 Όπότε : και New-DatabaseAvailabilityGroupNetwork -DatabaseAvailabilityGroup ContosoDAG -Name Backup -Description "Backup Network" -Subnets 192.168.0.0/16 -ReplicationEnabled:$True Δίνουμε και την Group IP: Και τώρα μπορούμε να προσθέσουμε τον 2ο server μας στο DAG. Aς δημιουργήσουμε τώρα τις 3 databases: Ελέγχουμε ότι όλα πήγαν καλά: Get-MailboxDatabaseCopyStatus Τις κάνουμε mount: Και τις προσθέτουμε στο DAG έτσι ώστε να γίνουν replicate και στον άλλον server: Έλέγχουμε την κατάσταση του replicatation: Και αφού όλα είναι εντάξει κάνουμε το replication: Βάζουμε mailboxes στις DAG databases. Ελέγχουμε την κατάσταση του Move Request: Εφόσον πάρουμε status “Completed” μπορούμε να κάνουμε remove το request: Υπάρχουν όμως και κάποια “κρυφά” mailboxes: Τώρα μπορούμε να σβήσουμε τις default mailbox databases. Ελέγχουμε και το replication health status για να δούμε ότι όλα πάνε καλά: Με την επιτυχή ολοκλήρωση του παραπάνω έχουμε 3 databases και ένα πλήρως λειτουργικό DAG περιβάλλον . Στο επόμενο post θα δούμε την δημιουργία mailboxes για τους πελάτες μας.

Ερώτηση: Γιατί δεν κάνεις query στο lastLogonTimeStamp - lastLogon attribute στο AD και να τους σβήσεις από εκεί?. Προφανώς για να κάνει login στο mailbox θα πρέπει να έχει κάνει login και στο Domain. Σε αντίθετη περίπτωση που οι χρήστες κάνουν login μέσω OWA μπορείς να κάνεις το εξής πιο πρακτικό: Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | Where {$_.LastLogonTime -lt (Get-Date).AddDays(-100)} | FT DisplayName,LastLogonTime > Koko.txt και μετά από AD Powershell να χρησιμοποιήσεις το koko.txt ώς input στην disable users command. []

Καλησπέρα, χρη 1) Το μόνο που θα μπορούσες να κάνεις θα ήταν να κάνεις split το load των mailboxes σε 2 ή περισσόυτερες βάσεις ανάλογα με την έκδοση του Exchange χρησιμοποιείς. Το offline defrag είναι μια διαδικασία που πέρνει αρκετές ώρες ανάλογα με το μέγεθος της βάσης σου και κατά την διάρκεια του οποίου οι χρήστες δεν έχουν access στα mail καθώς η βάση είναι dismounted.Όποτε 2) Υπάρχουν 2 τρόποι : Α) Exchange 2010 με DAG που είναι η απόλυτη λύση στο πρόβλημα σου ή σε περίπτωση που μείνεις σε 2007 κάποια λύση LCR ή CCR. Από περιεργεια και μόνο: Πόση είναι η βάση σου και πόσο το average size των mailbox ?

Πρίν απο λίγο έγινε μία ευχάριστη ανακοινώση που επιβεβαίωσε κάτι που είχα πει σε παλαιότερο post μου:"Τhe Microsoft Exchange team is enhancing positioning by including additional supported scenarios regarding Exchange Server 2010 running under hardware virtualization software. As of today, the following support scenarios are being updated, for Exchange 2010 SP1, and later:Combining Exchange 2010 high availability solutions (database availability groups (DAGs)) with hypervisor-based clustering, high availability, or migration solutions that will move or automatically failover mailbox servers that are members of a DAG between clustered root servers, is now supported." Όπως μπορείτε να καταλάβετε λοιπόν θα υπάρχουν πλέον και high available Dagged mailbox servers κάτι που δεν υπήρχε μέχρι σήμερα θέτοντας αρκετούς περιορισμούς στο Design. Μείνετε συντονισμένοι για περισσότερες λεπτομέρειες εντός των ημερών. Το πλήρες κείμενο της ανακοίνωσης θα το βρείτε εδώ . Πίσω στο σχεδιαστήριο λοιπόν...

You’ve told us that one of your top concerns is the increasing diversity of mobile devices that employees use to access your company resources. While many of these devices use Exchange ActiveSync (EAS) for mobile email, we all know that not all EAS clients are created equal. Exchange ActiveSync policies and features aren’t consistently implemented by licensees, so it can be challenging to find out what’s supported on each device. Today, we launched the Exchange ActiveSync Logo Program to establish baseline for EAS functionality in mobile email devices . The program is designed for device manufacturers that license the EAS protocol from Microsoft for use in mobile email clients that connect to Exchange. Wireless carriers may also join the program to include the Exchange brand to identify compliant devices for end-users. See Exchange ActiveSync Protocol for a list of current EAS licensees. This qualification program includes a test plan defined by Microsoft and a third-party lab to qualify implementations by handset makers. Qualifying clients must use EAS v14 or later, and implement the following features and management policies. Information on these and other EAS features can be found in Exchange documentation on TechNet: Direct Push email, contacts & calendar Accept, Decline & Tentatively Accept meetings Rich formatted email (HTML) Reply/Forward state on email GAL Lookup Autodiscover ABQ strings (device type and device model) provided Remote Wipe Password Required Minimum Password Length Timeout without User Input Number of Failed Attempts All Windows Phone 7 and Windows Phone 6.5 devices are compliant, as are Nokia devices running Mail for Exchange 3.0.50, including the Nokia E7, and Apple devices running iOS 4, including the iPhone 4, iPhone 3GS, iPad and iPad 2. We have a healthy pipeline of mobile device manufacturers ready to join the program and plan to announce additional participants in the coming months. Over time, the program will evolve to require additional features and management policies. We hope this program is a first step in helping you manage mobile email devices in your enterprise. For more info on managing your organization’s EAS devices, check out the previous post: Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list. Greg Smiley Senior Product Manager Exchange Product Management

Θέλοντας να μπω κι εγώ στο κλίμα του Cloud και ερχόμενος αντιμέτωπος με εταιρείες που θέλουν μεν cloud αλλά θέλουν και να το διαχειρίζονται κιόλας εξυπηρετώντας τους πελάτες τους. Ήρθα αντιμέτωπος με το θέμα του mail-hosting. Όπως ξέρετε υπάρχουν πολλές εταιρείες που προσφέρουν mail-hosting σε Exchange servers . Στην σειρά αυτή των Posts θα δούμε πως μπορούμε να υλοποιήσουμε ένα τέτοιο σενάριο. Το περιβάλλον που θα δημιουργήσουμε θα αποτελείται από: * 2 x 1 Hub Transport Role * 2 x 1 CAS + Mailbox Role Ας ξεκινήσουμε λοιπόν. Το πρώτο πράγμα που θα πρέπει να κάνουμε είναι να κατεβάσουμε τον Microsoft Exchange Server 2010 SP1: http://www.microsoft.com/downloads/details.aspx?FamilyID=50b32685-4356-49cc-8b37-d9c9d4ea3f5b&displaylang=en Η εγκατάσταση του Exchange σε Hosting mode γίνεται μόνο από command line καθώς δεν υπάρχει κάποιο GUI περιβάλλον. Ανοίγουμε λοιπόν cmd και ξεκινάμε: servermanagercmd /ip Exchange-All.xml Βέβαια μπορείτε να χρησιμοποιήσετε και την εντολή: C:\ExchangeSP1>Setup.com /mode:Install /roles:CA,HT,MB /hosting /organizationname:hosting Αφού τελειώσουμε την εγκατάσταση θα πρέπει να ρυθμιστεί και η υπηρεσία NetTcpPortSharing ώστε να ξεκινάει αυτόματα: Από powershell : Set-Service NetTcpPortSharing –startuptype Automatic Επίσης θα χρειαστούμε τα Remote Server Administration Tools: Από powershell : ServerManagerCmd -i RSAT-ADDS Κατά την διάρκεια της εγκατάστασης θα μας ζητηθεί και το Office 2010 filter pack. http://www.microsoft.com/downloads/details.aspx?familyid=5CD4DCD7-D3E6-4970-875E-ABA93459FBEE&displaylang=en Ξεκινάμε λοιπόν την εγκατάσταση και εγκαθιστούμε τον 1ο Hub Transport Server μας: setup.com /mode:install /role:HT,MT /organizationName:HostedExchange /hosting Για όσους αναρωτιούνται για τις διαφορές έχει το schema του Active Directory ενός “ κλασικού “ Exchange από έναν Hosted: Όπως μπορείτε να δείτε υπάρχει ένα καινούργιο CN container το ConfigurationUnits. Η εγκατάσταση μας έχει ολοκληρωθεί και έχουμε τον 1ο μας Hub Transport Server: Επόμενος στην σειρά είναι ο CAS και ο Mailbox server. Αυτοί οι 2 servers-ρόλοι έχουν κάποια προαπαιτούμενα hotfixes τα οποία έχουν ενσωματωθεί στο Windows 2008 R2 Server Service Pack 1. ( Ακόμα δεν το έχετε βάλει??? ) : KB982867 http://code.msdn.microsoft.com/KB982867 KB979744 http://code.msdn.microsoft.com/KB979744 KB983440 http://code.msdn.microsoft.com/KB983440 KB977020 http://code.msdn.microsoft.com/KB977020 Ξεκινάμε λοιπόν το installation των ρόλων από command line: setup.com /mode:install role:CA,MB,MT/organizationName:HostedExchange /hosting Την ίδια διαδικασία επαναλαμβάνουμε για την εγκατάσταση και των υπολοίπων server του περιβάλλοντος μας.. Στο επόμενο post θα συνεχίσουμε με τις αρχικές ρυθμίσεις.

Η βάση σου γίνεται dismount 5 η ώρα κάθε δεύτερη μέρα. Το σύστημα δουλεύει ως εξής: Ο exchange ελέγχει το database size κάθε μέρα στις 5 το πρωί.Αν το μέγεθος έχει ξεπεράσει το όριο δημιουργεί ένα warning event του τύπου: Event Type: Error Event Source: MSExchangeIS Mailbox Store Event Category: General Event ID: 9690 Date: 4/1/2011 Time: 5:00:33 AM User: N/A Computer: KOYKOYROYKOYPOKEMON Description: Exchange store 'First Storage Group\Mailbox Store': The logical size of this database (the logical size equals the physical size of the .edb file and the .stm file minus the logical free space in each) is 18 GB. This database size has exceeded the size limit of 18 GB. Την επόμενη μέρα στις 5 πάλι εάν αυτό συνεχίζει τότε η βάση πέφτει αυτόματα. Εσύ κάνοντας reboot τον server απλά κάνεις reset αυτόν τον τρόπο τεινά timer του Exchange. Τα σχετικά registry keys που θα πρέπει να πειράξεις είναι τα: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Public-Public Store GUID Θα χρειαστείς LDP ή ADSIEDIT. Το σχετικό link Επίσης βάλε την βάση στα 75GB και δες αν θα το ξανακάνει.

Είναι πολύ πιθανόν να ισχύει αυτό που αναφέρω εδώ: http://autoexec.gr/blogs/i-away/archive/2010/05/05/domain-keys-exchange-server.aspx Τσέκαρε το και ενημέρωσε μας.

Εφόσον είδες error 1018 τότε τα πράγματα αλλάζουν.. Έχεις 2 επιλογές : 1) Κάνεις restore το τελευταίο Backup και κάνεις replay τα logs. 2) Χρησιμοποιείς το eseutil χάνοντας κάποια ( απροσδιόριστο πόσα ) δεδομένα. Με τον πρώτο τρόπο δεν χάνεις δεδομένα αρκεί να έχεις κάποιο valid backup όσο πιο πρόσφατο γίνεται. Άλλα επειδή δεν μπορώ να μην δεν ρωτήσω.. όταν λες δοκίμασες με άλλο τρόπο να πάρεις backup τι ακριβώς εννοείς??

Όχι . Πρώτα θα δεις τον Event Viewer για αναφορές με Error 10062 και 1018. Αν υπάρχει 1018 αντιμετωπίζεται διαφορετικά. Δες το και ενημέρωσε μας για να προχωρήσουμε.

Δες λίγο τον Event Viewer σου πριν τρέξεις οτιδήποτε . Λογικά θα σου έχει βγάλει κάπου 10062 ( Corruption Detected ) και επίσης αν έχεις κάπου 1018 γιατί αλλάζει ο τρόπος αντιμετώπισης.

Τίποτα πιο ωραίο από μία corrupted database [] .Aνοίγεις Exchange Management Shell και αυτό που θα χρειαστείς είναι το εξής: New-PublicFolderDatabaseRepairRequest -Database <DatabaseIdParameter> -CorruptionType <PublicFolderDatabaseCorruptionType[]> [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]. Συμπληρώνοντας αντίστοιχα τα πεδία που θέλεις. Χρήσιμα επίσης είναι τα: New-PublicFolderDatabaseRepairRequest -Database <DatabaseIdParameter> -CorruptionType ReplState -DetectOnly και Get-help New-PublicFolderDatabaseRepairRequest -examples. Την πρόοδο και τα αποτελέσματα θα τα δεις απο τον Event Viewer: 10047 A mailbox-level repair request started 10064 A Public Folder repair request started 10048 The repair request successfully completed. 10050 The mailbox repair request task skipped a mailbox . 10059 A database-level repair request started. 10062 Corruption was detected. Κάντο και ενημέρωσε μας για τα αποτελέσματα.

Καιρός ήταν. Άντε να το βάλουμε και επίσημα στην παραγωγή!

Στα περιβάλλοντα που εργαζόμαστε οι περισσότεροι έχουμε ρυθμίσει το Outlook να εργάζετε στο λεγόμενο Cached Exchange Mode. Η ενημέρωση του Offline Address Book γίνεται απο default 1 φορά ανά 24 ώρες. Ο συνδυασμός αυτών των 2 λειτουργιών προκαλεί κάποιες φορές 2 σημαντικά προβλήματα: 1) Οι αλλαγές που κάνουμε στο Active Directory δεν εμφανίζονται στους clients 2) Δημιουργούνται Sync Errors ( Sync Issues Folder) Ποιά είναι λοιπόν η διαδικασία που πρέπει να ακολουθήσουμε όταν παρατηρούμε τέτοια συμπεριφορά?. 1) Βεβαιωνόμαστε ότι η GAL (Global Address Book) είναι όντως ενημερωμένη. Αυτό γίνεται στον Exchange 2003 πηγαίνοντας στον Exchange System Manager στον 'Recipients' folder επιλέγοντας 'All Global Address Lists' - 'Default Global Address List' - 'Properties' και πατώντας 'Preview'. Στον Exchange 2007/2010 αυτό θα πρέπει να γίνει χρησιμοποιώντας το OWA. Σε Outlook 2003, 2007,2010 που δουλεύουν σε cached mode ή με Offline folders χρησιμοποιείται το OAB που γίνεται download απο τον Exchange Server 1 φορά ανά 24 ώρες ή κάθε φορά που ξεκινάει το Outlook. Για να δούμε πως μπορούμε να επηρεάσουμε και να επιταχύνουμε την διαδικασία. 1α. Με το Rebuild του Address Book. Στον Exchange 2003 αυτό γίνεται απο τον 'Exchange System Manager' στο tab 'Recipients' folder, επιλέγοντας rebuild απο την καρτέλα 'Offline Address Book'. Στον Exchange 2007/2010 γίνεται με από το 'Exchange Management Shell' με την: get-offlineaddressbook | update-offlineaddressbook 2α. Ξανακατεβάζοντας χειροκίνητα το ΟΑΒ στο Outlook. Αυτό γίνεται από το 'Tools' - 'Send Recieve' - 'Download Address Book'. 2) Μπορούμε να επιταχύνουμε το χρόνο που ο Exchange Server κάνει Update την ΟΑΒ πειράζοντας το 'Update Interval' από το 'Exchange System Manager' – 'Recipients' - 'Offline Address Lists' . Με την παραπάνω διαδικασία μπορούμε να ξαναδημιουργήσουμε και να ενημερώσουμε την OAB τόσο στον server όσο και στους clients.

NOTE: The Exchange IPD Guide was updated to version 1.1 on July 11, 2011. The updates include content bug fixes, and updates related to the Exchange virtualization support changes. The download links are the same as Exchange IPD 1.0, so simply re-download the file to obtain the updated version. The Solution Accelerators team has released a new guide for Microsoft Exchange Server 2010 with Service Pack 1. The Infrastructure Planning and Design (IPD) Guide for Microsoft Exchange Server 2010 with Service Pack 1takes the IT architect through a step-by-step process for successfully designing an Exchange Server 2010 infrastructure. Exchange Server 2010 supports a variety of infrastructure topologies that enable IT departments to deploy the messaging architecture that best suits their business needs. This guide will help organizations make informed decisions about the design of fault tolerance and scalability so that their overall requirements are met. The guide covers these key steps in the Exchange Server 2010 infrastructure design process: Defining the project scope by identifying your individual business and IT requirements for a messaging infrastructure. Mapping features and functionality based on the defined scope to develop the appropriate Exchange Server 2010 design. Designing the infrastructure and role requirements for the proposed Exchange Server 2010 architecture. Determining the sizing, fault tolerance, and physical placement of Exchange Server 2010 roles. The IPD Guide for Microsoft Exchange Server 2010 with Service Pack 1 can help you reduce planning time and costs, and ensure a successful rollout of Exchange Server 2010 - helping your organization to more quickly benefit from this flexible and reliable messaging platform. Next Steps Download the FREE Exchange Server 2010 guide (ZIP - 2.94 MB) Download other best practices from the Infrastructure Planning and Design series for products such as Microsoft Forefront Unified Access Gateway, Windows Server 2008 R2, Hyper-V, SQL Server 2008, Exchange Online, SharePoint Online, System Center, and much more from the IPD site on TechNet. Visit the Exchange Server 2010 site on microsoft.com to learn more. Check out other Solution Accelerators to help you solve your deployment, planning, and operational IT problems. More information about the IPD series Planning the next generation of technical infrastructure for corporations can be a complex and daunting task. The success of any infrastructure is measured in how well the design choices match business objectives. Although plenty of product documentation is available, it can be difficult to find guidance on how to appropriately plan the core infrastructure for an organization. The Infrastructure Planning and Design series is designed to present the technical decision maker with the most concise planning guidance for Microsoft technologies. It also provides a means to validate design decisions to ensure that the selected solution meets the requirements of both business and IT stakeholders. The IPD documents are designed to be used by the following IT personnel: Infrastructure architects and planners who have a firm operational grasp of the technology Partners and consultants who design infrastructure solutions Business managers who want to understand how the decisions being made about technology both support and affect the business Check out all the Infrastructure Planning and Design team has to offer! For additional information, including our most recent guides, visit the IPD page on TechNet — http://www.microsoft.com/IPD. We appreciate your comments and feedback; please send mail to [email protected].

Και μιας που η δίψα σας για γνώση φαίνεται άσβεστη ας βάλω κι εγώ ένα λιθαράκι: Απο τις 6 Φεβρουαρίου ( Κυριακή ) 19:00 - 20:00 ξεκινάνε οι Greek Exchange Nights στο πνεύμα των υπολοίπων Greek Live Nights. Θα ξεκινήσουμε από απλά βασικά πράγματα και θα φτάσουμε μέχρι Advanced και out of space καταστάσεις. Ο λόγος που επιλεχθηκε η κυριακή είναι λόγω υποχρεώσεων και εργασίας. Μπορείτε να κάνετε register και να συνδεθείτε εδώ

Πρώτο post για το 2011 και ξεκινάει με χαρούμενα νέα. Από ανέκαθεν υπήρχαν διάφοροι τρόποι με τους οποίους οι χρήστες του Exchange Server μπορούσαν να δούν τμήματα μόνο της Global Address List (GAL). Αυτή η δυνατότητα μας βοηθούσε στο να διατηρούμε ένα μπούσουλα ειδικά σε μεγάλα Exchange Organizations χωρίς να στερούνται δυνατοτήτων όπως Public Folders, Transport Rules ή High Availability. Ο τρόπος που γινόταν αυτό διαφοροποιούταν από έκδοση σε έκδοση του Exchange μέχρι τώρα όμως δεν υποστηριζόταν στον Exchange 2010. Αυτό όμως έρχεται να αλλάξει. Το Exchange Team δουλεύει ήδη στην απευθείας ενσωμάτωση Global Address Segmentation δυνατοτήτων που θα έχουμε την χαρά να έχουμε και μάλιστα με γραφικό περιβάλλον στο επερχόμενο Service Pack 2 στα τέλη του 2011 ( Περισσότερες πληροφορίες λίαν συντόμως! ). Αποτέλεσμα του παραπάνω είναι ότι δεν θα δημοσιευτεί το καθιερωμένο Configuring Virtual Organizations and Address List Segregation Whitepaper ενημερωμένο για τον Exchange Server 2010, όπως στον Exchange Server 2007. Επειδή το τοπίο θα παραμείνει σχετικά θολό και δεν θα αποκαλυφτούν πολλά μέχρι την έλευση του Service Pack 2 ένα sneak peak του scope πάνω στο οποίο θα κινηθούν ενσωματώνοντας την δυνατότητα αυτή στον Exchange Server είναι το εξής: Το GAL Segmentation δεν θα αντικαταστήσει την multi-tenant enabled version του Exchange 2010. Η δυνατοτότητα αυτή θα απευθύνεται κυρίως σε: Εταιρείες που θέλουν κατακερματισμό του address book τους για διάφορους λόγους. Δυνατότητα sharing resources μεταξύ των χρηστών. Έλεγχος του τι θα βλέπει ο χρήστης όταν ανοίγει το address book. Αυτό θα γίνει μέσω ενός "Address Book Policy" αντί για το μέχρι τώρα ACL based GAL Segmentation που χρησιμοποιούσαμε. Παρόλα αυτά δεν θα είναι το ίδιο όπως σε κατάσταση Hosting mode του Exchange 2010 SP1. Περισσότερες πληροφορίες Σύντομα!. Stay Tuned. Source: Microsoft Exchange Product Group.

http://autoexec.gr/blogs/i-away/archive/2009/05/18/multiple-smtp-hosting-on-exchange.aspx . Νομίζω ότι θα σου λύσει όλες τις απορίες.