|
Cached Exchange Mode in a Remote Desktop Session Host environment: planning considerations is a technical whitepaper recently released by Microsoft.
Historically, Microsoft Outlook has only been supported in an RDSH environment when it is deployed in Online Mode and connected to a Microsoft Exchange Server. This is still the recommended configuration for Microsoft Outlook 2010 when it is deployed in an RDSH environment. However, customers who deploy Outlook 2010 now have the supported option of enabling Cached Exchange Mode when Outlook 2010 is installed in a Remote Desktop environment. Cached Exchange Mode might be ideal for deployments in which Outlook is connecting over a high latency connection to an Exchange server that is located remotely. For the relatively few users who access Outlook through a remote desktop, this might be the ideal configuration. However, Online Mode against the Exchange server is still the most scalable and optimized configuration for large deployments.
This white paper covers three major areas that you should consider when you deploy Outlook 2010 with Cached Exchange Mode in a Remote Desktop environment:
- Storage footprint
- Performance impact
- Networked Storage
|
|
Last few months I've been working on a project for one very big Canadian Company.
Now I can say that this project is coming to the end :).
I was concentrated on building a solution for fully unattended deployment procedure of Windows Server 2008 Servers and Windows 7 Workstation.
In total this project covers 200 Servers and about 1000 Workstation. I've used a lot of tricks and tips in this project and built a lot of scripts to automate EVERYTHING :).
Today I asked myself, "How many lines of code you wrote in all scripts for this project?"
So, after very simple maths I can say, all my scripts for FULLY UNATTENDED Windows 2008 and Windows 7 system contain 1227 lines :).
|
|
I've already mentioned many time that I'm disabling IPv6 almost on all my servers and workstation.
In today days, I really don't see a reason to have it enabled (maybe in next few years, but not now).
If you search my site you will find few ways how is possible to disable IPv6. Personally, I'm preferring to disable it systemwide, it means I disable IPv6 as a component. Here is how I do that.
Let's see today how to disable / enable IPv6 via Group Policy (GPO)...
|
|
|
Read more...
|
Aidan Finn published on his blog very interesting post. He named it "Interview Questions … To Ask The Interviewer".
I totally agree with Adam and decided to republish his post here, at CuruIT.com :)
|
|
|
Read more...
|
When Microsoft has released a Hyper-V the first question that I've asked myself was "How do I Backup / Replicate Hyper-V?"
In VMWare world one of the best applications for replication is Veeam, but they have nothing for Hyper-V.
|
|
|
Read more...
|
|
The short answer is: Everything just works.
The long answer is as follows:
Prior to Window Server 2008 R2 (namely in Windows Server 2008) you could run into a couple of problems. In Windows Server 2008 R2 Microsoft has implemented a Sysprep provider to ensure that everything goes smoothly. This provider does work during two of the phases of Sysprep:
Generalize
The generalize phase of Sysprep is where an installed version of Windows is prepared to be duplicated – and all installation specific information is removed. During this phase Hyper-V makes a couple of key changes:
- The installation date information for Hyper-V cleared. It will be automatically regenerated when the system image is deployed to a new system (or rebooted locally).
- The dynamic MAC address range is cleared. This will also be automatically regenerated when the system image is deployed to a new system. This step is necessary to ensure that you do not get duplicate MAC addresses on multiple Hyper-V servers if they are all deployed from the same base image.
Specialize
The specialize phase is run after the system image has been deployed to a new computer. Hyper-V makes the following change as part of this phase:
- Enable automatic launching of the hypervisor in the boot configuration data (BCD) store. Because a new boot configuration data store is created as part of the image deployment process, and because Hyper-V stores information in the boot configuration data store – we need to make sure this information comes across to the new system.
|
|
|
Learn how you can utilize MED-V to virtualize your web applications which require Internet Explorer 6 or 7 in your environment. If your organization is considering an upgrade to Windows 7 or Internet Explorer 8 but is concerned about the expense, time, and IT staff effort needed to update your older (or legacy) LOB web applications, using a virtualization option might be a an effective solution until you can run your web applications natively with IE 8. Learn more about the other virtualization options:
|
|
|
Read more...
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
