As we have seen in Setting up an Event Collecting Computer you can use either Http or Https protocol to transfer data from the forwarding to the collecting computer. Although standard Http transport uses encryption for forwarded events, you can configure event forwarding to use the encrypted Https protocol. However, using Https requires the following additional tasks to be performed on the forwarding computers: You need to install a certificate. You can do this automatically in Active Directory environments by using an enterprise CA. You need to create a Windows Firewall exception for TCP port 443. If you opted to minimize bandwidth or latency in the collecting computer's Advanced setting – Event Delivery Optimization, then you must also add a Https firewall exception rule and install a certificate on the collecting computer. At an elevated command prompt type: winrm quickconfig – transport:https Finally, from the Advanced Subscription Settings on the Collecting computer you need to click the Protocol: drop-down arrow and select HTTPS as show below:
REDMOND, Wash. — Feb. 16, 2011 — Microsoft Corp. (Nasdaq "MSFT") today announced that Microsoft Dynamics CRM 2011 for on-premises and partner-hosted deployments has been completed and released for customer download. This release complements the latest version of Microsoft Dynamics CRM Online, which delivers Microsoft Dynamics CRM 2011 as an on-demand service from Microsoft's datacenters and was launched into 40 markets and 41 languages in January. With a single multitenant code base across cloud and on-premises deployment models, Microsoft Dynamics CRM 2011 delivers the Power of Productivity to sales, service and marketing organizations worldwide. Microsoft Dynamics CRM 2011 is now globally available and existing customers with active Microsoft Software Assurance agreements can access the new version immediately via theMicrosoft Download Center. In addition, Microsoft announced the new release scaled to 150,000 concurrent users in a single instance while delivering sub-second response times, once again raising the bar for performance and scalability in the CRM industry. The new benchmark results will be detailed in a Microsoft Dynamics CRM performance and scalability white paper that will be delivered in the coming weeks. "The need to build deeper and more profitable relationships on a global scale remains a CIO top priority," said Mark Barrett, senior vice president, CRM, Avanade. "The combination of Avanade's deep experience in solution development and Microsoft Dynamics CRM 2011 enables us to deliver comprehensive CRM capabilities to our clients through on-premises deployments as well as a software-as-a-service offering. Microsoft Dynamics CRM 2011 provides a platform for us to help companies strengthen customer and partner relationships, increase productivity, and collaborate across the organization." Microsoft Dynamics CRM 2011 provides customers and partners with a wide range of benefits, including point-and-click configurability, enterprise scalability, and e
Events are collected or sent (when subscription configuration is set to normal) every 15 minutes which is quite adequate for normal operations; however, there might be critical periods for some resources that we need to reduce this delay and get critical events faster. As already noted in Setting up an Event Collecting Computer, with the help of the wecutil command-line tool we can modify this parameter. The wecutil syntax is as follows: wecutil ss "subscription_name" /cm:custom wecutil ss "subscription_name" /hi:<milliseconds_delay> where the only parameters you need to specify are the subscription name and the delay in milliseconds, for example: wecutil ss "Test Subscription" /cm:custom wecutil ss "Test Subscription" /hi:30000 would set our current subscription called "Test Subscription" to 5 minutes intervals. The interval parameter is called HeartbeatInterval as shown below: To display the current configuration, at an elevated command prompt type: wecutil gs "Test Subscription" For a full list of the wecutil command options type wecutil /? at the command prompt.
HP today announced a comprehensive service that simplifies the process of designing and building data centers by offering design, construction and project management from a single vendor. The new HP Critical Facilities Implementation service (CFI) can lower clients' cost of ownership by providing a single integrator that delivers all the elements of a data center design-build project from start to finish. An extension of the HP Converged Infrastructure strategy, HP CFI is an architectural blueprint for the data center of the future that allows clients to align and share pools of interoperable resources. A recent Gartner survey(1) indicated that "a total of 46 percent of our respondents report that they will build one or more new data centers in the next two years, and 54 percent expect that they will need to expand an existing data center in that time frame." Using HP's turnkey offering, clients can realize faster implementation times and lower costs to expand their computing capacity. "Constructing a data center is an enormous undertaking for any business, and taking an integrated approach with a single vendor will help maximize cost and efficiency, while reducing headaches," said Dave Cappuccio, research vice president, Gartner. "As customers' data center computing requirements add complexity to the design-build process, comprehensive solutions that provide clients with an end-to-end experience will allow them to realize their plans within the required timeframe and constraints." HP client HNA Group is a large multi-enterprise organization in China, encompassing air transportation, tourism services, logistics and financial services. "As our business portfolio continues to expand, we needed to quickly create a new data center that complied with international standards," said Li-Chao Tang, general manager, Information Technology Management, HNA Group. "HP provided us with end-to-end support for our new facility, providing first-class data center design and technolog
Having set up all remote hosts that you will be retrieving Events from, it is time to configure the Collecting workstation. The collecting computer would normally be an admin computer running Windows Vista, Windows 7 or Windows Server 2008. Assuming our collecting computer is named env1client01 then, from an elevated command prompt type: wecutil qc This command will set Windows Event Collector service from Manual to Delay-Start. Next, we need to create an Event Subscription as follows: Open Event Viewer on evn1client01 (Collecting computer), right click Subscriptions and select Create Subscription. A Subscription Properties window should appear as shown below, type a name and a description: There are two types of Subscriptions, you can use the default type: Collector initiated – where the collecting computer contacts the source computers to retrieve events. I suggest that you test the added computers by clicking the Test button from the Select Computers… option. Source computer initiated – where all forwarding computers send events to the Collecting computer. Non-domain computers need to have a certificate installed to be able to connect successfully, in fact, domain related issues will prevent proper flow of events! Next, click Select Events… button and define the error criteria such as, levels, log, source, etc. that will be used to match and collect events. The Advanced… button loads optional settings which are: User Account – whether you want to use specific user or machine account. The account must be a member of the forwarding computer's Event Log Readers group. Event Delivery Optimization – where you can save the bandwidth consumed (when monitoring over a WAN) or force a push delivery mode to get events faster (when monitoring critical services) or use the default normal behavior which ensures a reliabl