May 2007 - Posts
I got some of the requirements from the customers and They always ask the same questions.
"Can I store the Printer/PC Support Maintenance Contracts?"
"Is it provide incident logging for my helpdesk?"
"Can I keep the Purchase Order together?".....
These are the common questions from SME customers. Because there are no different teams for handle Incident Management and Changes/Configurations Management for their organization.
For the Enterprise Customers, HelpDesk Handle the Incident Management tasks, and Infrastructure Team Handle the Changes/Configurations Management tasks.
However, System Center Service Manager addressed the needs for Enterprise Customers, But I don't think it is a good solution for SME customers. (Based on their $$$, scale and the required functions).
So, I developed a Windows Sharepoint Service 3.0 Site with the following features to address the needs from SME:
-
Single Interface
-
Incident Logging
-
Store the Purchase Order, Status Reports (XML with Infopath)
-
Inventory Reports (WebPart and SMS Reporting)
-
Remote Desktop (WebPart and RDP Web Connection)
-
Schedulling
-
Tasks Assignment and Notifications (Web, Email and RSS)
What other features i should add into this solution for SME?
Please leave your comments and suggestions to me. Any feedbacks are welcome.
Inventory Tool for Microsoft Update unable to download the Update Catalog successfully
Microsoft Update Tool Sync Advertisement failed and unable to download the Update Catalog when you are using Proxy Server to access Internet. And you got the message ID 11456 in the Advertisement Status of Microsoft Update Tool Sync. Also, in WUSSyncXML.log, there are records like "User Account:NONE".
For the Solution, Please read: http://support.microsoft.com/kb/555926
I wrote this guide in the last year, and finally, i can publish it on the web and share with everyone.
You can download it from here and it will be published on Microsoft WebSite Later
Enjoy it!
|
Monitored Item |
Recommended Limit |
| Simultaneous Operations Consoles |
50 |
| Agent monitored computers reporting to a Management Server |
2,000 |
| Agent monitored computers reporting to a Gateway Server |
200 |
| Agentless Exception Monitored computers per Management Server |
25,000 |
| Agentless Exception Monitored computers per Management Group |
100,000 |
| Collective Client Monitored computers per Management Server |
2,500 |
Microsoft System Center Essentials 2007 is a proactive and unified management solution that enables IT professionals in midsize organizations to more efficiently secure, update, monitor and troubleshoot their IT environments.
Essentials 2007 provides:
• Proactive monitoring, troubleshooting and asset tracking to keep your IT environment secure and up-to-date
• A unified solution with a single console for managing your servers, clients, hardware, software, and IT services
• Efficient execution of complex management tasks like troubleshooting end user issues, monitoring, and server and client software deployment
Download
Microsoft Systems Management Server (SMS) 2003 R2 with Service Pack 3 (SP3) brings organizations full lifecycle support for Microsoft’s latest platform including software distribution, update services and inventory are available to the Vista client.
Adding optional capabilities to enhance the software and hardware inventory functionalities provided in SMS 2003, SP3 provides information to help organizations to make better business decisions about their IT assets. Through a new library of over 400,000 software titles, SMS 2003 SP3 provides an option to augment existing SMS inventory capabilities with deeper asset intelligence. SMS SP3 provides rich reporting about installed applications and hardware enabling better license reporting, software consolidation and upgrade planning.
Download
-
Local Management Group and Connected Management Group=2 Tier Only, CMG and CMG can't communicate.
-
Raise the Domain Functional Level to other than Windows 2000 Mixed before deployment. No Limitation for Forest Functional Level.
-
Agent/Server mutual authentication is mandated in Operations Manager 2007 for all agent/server communication
-
The certificates used for untrusted Domain scenario must ultimately trust the same root certification authority (CA)
-
Install and add the Gateway Server in the Untrusted Domain.
-
Create a domain security group for the Operations Manager Administrators role before deployment
-
Windows Installer 3.1 required for Agent Installation
-
An agentless managed device must not be separated from its Management Server or proxy agent by a firewall because monitoring is performed over RPC.
-
The action account of the agent that is performing the monitoring must have local administrative rights on the device that is being monitored.
-
Operations Manager 2007 requires SQL Server 2005 Enterprise edition for Audit Collection Services Database
-
SQL Server 2005 SP1 and Cumulative Hotfix Package (build 2153) for SQL Server 2005 required
-
Required to use SQL Server Windows Authentication mode
-
To provide the best recovery experience, configure the OperationsManager database to run in the Full Recovery model
-
SQL Server Service Broker must be enabled
-
Keeping the OperationsManager Database relatively small ensures faster operations
-
SDK and Config Service Account should be Local System when install single Management Server in the environment.
-
Each ACS collector must have its own ACS database.
-
Run the ACS Installation on the ACS Collector.
-
A Gateway server should not be used as an AEM Collector except in the System Center Essentials configuration
-
Business-critical client monitoring allows business-critical clients to be deployed as watcher nodes and run synthetic transactions against IT services. In addition to event and performance data, business critical clients often require audit collection to ensure that compliance requirements are met
-
To use Active Directory to Automatically Assign Agents, Run MOMADAdmim.exe with the Appropriate Parameters to create the OperationsManager Container with the permission in AD. Create the Inclusion or exclusion rule on the management servers. And configure manual installed agent from reject to review