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
Microsoft Infrastructure
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
Subscribe to:
Posts (Atom)