v příkazovém řádku zadejte
tasklist /m *.dll
v příkazovém řádku zadejte
tasklist /m *.dll
In the case that you wasted on a server generates an error „Error communicating with the Spooler system service. Open the Services snap-in and confirm the Print Spooler That service is running.“
Strat-run-TSCC.MSC and right on the rdp-tcp connection – properties, and check the client settings (disable) Windows Printer Mapping and LPT port mapping.
Now you need to add value to the registry. „Watch you do this action at his own risk“ if you do not have a REGEDIT-em experience, preferring to drop into this. “
go to
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ WDS \ rdpwd
and create a key – a DWORD
name – fEnablePrintRDR with value 1, 0 disables the mapping of the client’s disk drives.
ASP.NET 2.0, 32-bit version
To run the 32-bit version of ASP.NET 2.0, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to enable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
(0=64bit , 1=32 bit )
Type the following command to install the version of ASP.NET 2.0 (32-bit) and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
Set SCOM 2007 to forward SNMP traps
Trapgen.exe : Used to generate the traps.
download trapgen.exe -http://trapgen.trapreceiver.com/ or you can find it in my OneDrive (accessible from this page ), folder tools (https://onedrive.live.com/?cid=A2DAD70E062C0112&id=A2DAD70E062C0112%2112099&authkey=%21ANIbXFTLL1i0y70)
SNMPTrap.exe : Used to check out snmp traps.( for this check , adjust destination IP address on local IP of SCOM server )
Settings:
Download or copy both tools on your SCOM server. I copy them in C:\SNMP\ folder.
In the console go to the Administration pane then select Settings and open Notification properties.
Go to the Command tab and click on Add.
The command line used is : C:\SNMP\trapgen.exe
The command line parameters are :
Where IP 192.168.12.130 is destination IP address of next monitoring server (Tivoli IBM) 192.168.15.201 is the IP address of my SCOM server
The initial directory is : C:\SNMP\
When you are done , create a new Notification recipient ( can be local user of SCOM server or domain user )
Select your notification command channel like below (delivery address is useless for us) and continue in N.D Wizard
So you have Recipient and last step will be how create Subsciption.
Make up new name for subscription and add your exist notification recipients for SNMP traps
On User role filter tab press next and here you can choose groups which you want to cover.
On Classes tab press next and here choose all ( press on check all button ) , if you want and finish the wizard.
Now you can check if your monitoring system 3rd side is geting snmp traps from SCOM2007
I have used it on my SCOM server and „without problems“
good web page – http://blogs.technet.com/b/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx
$Data/Context/DataItem/AlertId$ The AlertID GUID $Data/Context/DataItem/AlertName$ The Alert Name $Data/Context/DataItem/Category$ The Alert category (PerformanceHealth,PerformanceCollection,Operations,EventCollection,StateCollection,SoftwareAndUpdates,Alert,System,Custom,AvailabilityHealth,ConfigurationHealth,SecurityHealth,Discovery,NotificationCategory,Maintenance $Data/Context/DataItem/CreatedByMonitor$ True/False $Data/Context/DataItem/Custom1$ CustomField1 $Data/Context/DataItem/Custom2$ CustomField2 $Data/Context/DataItem/Custom3$ CustomField3 $Data/Context/DataItem/Custom4$ CustomField4 $Data/Context/DataItem/Custom5$ CustomField5 $Data/Context/DataItem/Custom6$ CustomField6 $Data/Context/DataItem/Custom7$ CustomField7 $Data/Context/DataItem/Custom8$ CustomField8 $Data/Context/DataItem/Custom9$ CustomField9 $Data/Context/DataItem/Custom10$ CustomField10 $Data/Context/DataItem/DataItemCreateTime$ UTC Date/Time of Dataitem created $Data/Context/DataItem/DataItemCreateTimeLocal$ LocalTime Date/Time of Dataitem created $Data/Context/DataItem/LastModified$ UTC Date/Time DataItem was modified $Data/Context/DataItem/LastModifiedLocal$ Local Date/Time DataItem was modified $Data/Context/DataItem/ManagedEntity$ ManagedEntity GUID $Data/Context/DataItem/ManagedEntityDisplayName$ ManagedEntity Display name $Data/Context/DataItem/ManagedEntityFullName$ ManagedEntity Full name $Data/Context/DataItem/ManagedEntityPath$ Managed Entity Path $Data/Context/DataItem/Priority$ The Alert Priority Number (High=1,Medium=2,Low=3) $Data/Context/DataItem/Owner$ The Alert Owner $Data/Context/DataItem/RepeatCount$ The Alert Repeat Count $Data/Context/DataItem/ResolutionState$ Resolution state ID (0=New, 255= Closed) $Data/Context/DataItem/ResolutionStateLastModified$ UTC Date/Time ResolutionState was last modified $Data/Context/DataItem/ResolutionStateLastModifiedLocal$ Local Date/Time ResolutionState was last modified $Data/Context/DataItem/ResolutionStateName$ The Resolution State Name (New, Closed) $Data/Context/DataItem/ResolvedBy$ Person resolving the alert $Data/Context/DataItem/Severity$ The Alert Severity ID $Data/Context/DataItem/TicketId$ The TicketID $Data/Context/DataItem/TimeAdded$ UTC Time Added $Data/Context/DataItem/TimeAddedLocal$ Local Time Added $Data/Context/DataItem/TimeRaised$ UTC Time Raised $Data/Context/DataItem/TimeRaisedLocal$ Local Time Raised $Data/Context/DataItem/TimeResolved$ UTC Date/Time the Alert was resolved $Data/Context/DataItem/WorkflowId$ The Workflow ID (GUID) $Target/Property[Type=”Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer”/WebConsoleUrl$ The Web Console URL Target/Property[Type=”Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer”/PrincipalName$ The principalname of the management server $Data/Recipients/To/Address/Address$ The name of the recipient (e.g. the Email alias to which the notification is addressed)
V případě že používáte MS Outlook a stalo se vám že jste si zazálohovali poštu do souboru .pst , nikdy si nemůžete být jisti že se soubor nepoškodí……. V případě že se vám nedaří .pst soubor naimportovat zpět do aplikace Outlook , existuje nástroj obsažený v MS Office 2003, 2007 … který jej umí spravit.
Jděte při standartní instalaci MS Office C:Program FilesMicrosoft OfficeOffice12SCANPST.EXE
nebo c:progra~1Microsoft OfficeOffice12SCANPST.EXE
spustítě .exe soubor a vyberete .pst který chcete opravit.
🙂 to vše