The SQL server 2000/2005 management packs are not pulling out the SQL Memory Manager performance matrices by default.
I've written this management pack to pull out the following counters on the SQL memory manager.
This MP is depending on the discovery management pack of SQL server 2000 and 2005.
https://www.microsoft.com/en-us/download/confirmation.aspx?id=15226
sathwet@gmail.com
- Sath Wetthasingha PGD(UK),Dip-BCS(UK),Dip-NCC(UK),MCSE,MCT,MCLC,MACS,MBCS,MCTS,ACIW
- Melbourne, VIC, Australia
- I’m specialized in Microsoft technologies and information security. I always willing to ride an extra mile to help the IT community sharing my past experience and technical knoladge.
Monday, May 30, 2016
Tuesday, March 20, 2012
How to migrate print queues from server 2003 to Server 2008
How to
migrate print queues from server 2003 to Server 2008
You can use
the printbrm command line tool for this purpose. But this tool doesn’t support
Server 2003 platform. You will have to run this tool with administrative privileges
on Windows 7 computer or on your server 2008 server.
Printbrm -s
\\ServerName -b -f 2003server.printerExport
After you
create the printerExport file just import it to your 2008 server.
Friday, February 24, 2012
Alert: Run As Account does not exist on the target system or does not have enough permissions
Alert: Run As Account does not exist on the target system or does not have enough permissions
When you install the OpsMgr SQL management pack, it will
keep chase for the rights to get in to SQL databases.
You can simply sort this by adding the “Management Server
Action “ account to SQL server admins group , if you have a group to manage the
SQL server rights or Simply assigning access rights for the management server action
account on the SQL database.
Friday, February 10, 2012
Port number came as “0” instead of the “9100”
I exported a large volume of print queues from the old
server and tried to import in to the new server. After import I found none of
the print queues prints and no errors on the event viewer.
Finally I found the issue, during the printbrm import the
port number came as “0” instead of the “9100” for some reason. Simply extracted
the printerexport file and changed the port to 9100 and imported it back
again. Please refer my Blog article Editing printerExport file for further information.
Monday, February 6, 2012
Editing printerExport file
You can extract the printerExport file using a compression utility such as winzip ,win rar or 7-Zip.
After hat you may edit the xml file as necessary.
You may use the notepad plus to open these xml files.
Then browse in the print server c:\windows\system 32\spool\ Copy the folder tools to your local computers c:\
Then execute the following command to pack it back again as a printExport file Printbrm -d c:\tools\prntmig -b -f a2.printerExport
After hat you may edit the xml file as necessary.
You may use the notepad plus to open these xml files.
Then browse in the print server c:\windows\system 32\spool\ Copy the folder tools to your local computers c:\
Then execute the following command to pack it back again as a printExport file Printbrm -d c:\tools\prntmig -b -f a2.printerExport
Monday, January 23, 2012
Friday, September 30, 2011
Wednesday, September 28, 2011
Process Monitor v2.96
http://technet.microsoft.com/en-us/sysinternals/bb896645
Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. It combines the features of two legacy Sysinternals utilities, Filemon and Regmon, and adds an extensive list of enhancements including rich and non-destructive filtering, comprehensive event properties such session IDs and user names, reliable process information, full thread stacks with integrated symbol support for each operation, simultaneous logging to a file, and much more. Its uniquely powerful features will make Process Monitor a core utility in your system troubleshooting and malware hunting toolkit.
Sharing
Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. It combines the features of two legacy Sysinternals utilities, Filemon and Regmon, and adds an extensive list of enhancements including rich and non-destructive filtering, comprehensive event properties such session IDs and user names, reliable process information, full thread stacks with integrated symbol support for each operation, simultaneous logging to a file, and much more. Its uniquely powerful features will make Process Monitor a core utility in your system troubleshooting and malware hunting toolkit.
Sharing
Sunday, September 25, 2011
Friday, September 23, 2011
Windows Print Cluster Migration error Windows Server 2008 R2
I had an issue with migrating large printer cluster to a new Microsoft Windows server 2008 R2 Cluster. All i did was export printers from the old cluster and import in to the new cluster. But the import keep failed with the following error on event viewer.
Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed to restore print queue HP LaserJet 8000dn. The restore process will continue, skipping this queue. Error: 0x80070709. The printer name is invalid.
I found Microsoft KB976571 fixes this issue and many other printer cluster related issues. I tested this my environment with no issues, But its highly recommended to test with a test cluster before you install it in the production.
Printbrm.exe (the Printer Migration Wizard or the command-line tool) failed to restore print queue HP LaserJet 8000dn. The restore process will continue, skipping this queue. Error: 0x80070709. The printer name is invalid.
I found Microsoft KB976571 fixes this issue and many other printer cluster related issues. I tested this my environment with no issues, But its highly recommended to test with a test cluster before you install it in the production.
http://support.microsoft.com/kb/976571
I found this blog helps a lot on Microsoft cluster related issues as well.
http://blogs.technet.com/b/askperf/archive/2010/11/12/windows-print-cluster-best-practices-for-windows-server-2003-to-windows-server-2008-r2.aspx
Thursday, September 15, 2011
Wednesday, September 7, 2011
PXE Service Point role
http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/index.jsp?topic=%2Fdpsccm%2Fdpsccm_t_setting_up_pxe_serv_pt.html
SCCM Create a baseline
http://blogs.kraftkennedy.com/index.php/2011/06/03/creating-the-sccm-dcm-baseline-for-laptop-security/
Adding a sccm configuration item
http://sysmgmt.wordpress.com/2011/02/25/setup-desired-configuration-management-in-sccm-2007/
Backup sccm
http://www.windows-noob.com/forums/index.php?/topic/750-how-can-i-backup-my-sccm-server/
Computers not reported in 30 days in SCCM
select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System where SMS_R_System.Name in (select Name from SMS_R_System where ((DATEDIFF(day, SMS_R_SYSTEM.AgentTime, getdate()) >=30) and AgentName = "SMS_AD_SYSTEM_DISCOVERY_AGENT")) and SMS_R_System.Name in (select Name from SMS_R_System where ((DATEDIFF(day, SMS_R_SYSTEM.AgentTime, getdate()) >=30) and AgentName = "Heartbeat Discovery"))
Tuesday, September 6, 2011
Configure throttling for BITS in System Center Configuration Manager SCCM 2007
http://www.youtube.com/watch?v=LN_8_gMNeyk
Subscribe to:
Posts (Atom)

