Selasa, 22 September 2015

Searching Message Tracking Logs by Sender or Recipient Email Address

Continuing my series of tips on searching message tracking logs using PowerShell, in this article I will demonstrate a few techniques for searching logs based on sender or recipient email address.
The Get-MessageTrackingLog cmdlet provides two parameters for specifying sender and recipient email addresses as search criteria.
  • -Sender – a single SMTP address for the sender of the email message
  • -Recipients – one or more SMTP addresses for the recipients of the email message
Both parameters are optional, so if they are omitted the search will return all senders, all recipients, or all of both.
To demonstrate the use of these parameters consider the following email message sent from Alan Reid to three recipients.

Searching Message Tracking Logs by Sender Email Address

Because I happen to have sent this test message within the last hour it is not very difficult for me to search for by combining the -Sender parameter with the -Start parameter to search within a time/date range.
[PS] C:\>Get-MessageTrackingLog -Sender Alan.Reid@exchangeserverpro.net -Start (Get-Date).AddHours(-1)

EventId  Source   Sender                            Recipients                        MessageSubject
-------  ------   ------                            ----------                        --------------
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Payroll report for September
RECEIVE  SMTP     Alan.Reid@exchangeserverpro.net   {David.Gower@exchangeserverpro... Payroll report for September
DELIVER  STORE... Alan.Reid@exchangeserverpro.net   {Alex.Heyne@exchangeserverpro.... Payroll report for September
DELIVER  STORE... Alan.Reid@exchangeserverpro.net   {David.Gower@exchangeserverpro... Payroll report for September
However, if I were searching over a broader time range I may see more results than I really want to see.
[PS] C:\>Get-MessageTrackingLog -Sender Alan.Reid@exchangeserverpro.net

EventId  Source   Sender                            Recipients                        MessageSubject
-------  ------   ------                            ----------                        --------------
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Descry turmoil deviance
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Impending abeyance recitals ba...
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Egress
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Presage visceral penurious
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Stipple voluble blatant stymie
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Inured
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Heinous mercurial
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Relapse smolder
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Meeting minutes
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Supine poignant
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Indigence denigrate swerve vig...
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Jocular
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Oblivious apropos condone savant
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Obdurate splice penitent
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Extenuate aplomb obtain eulogy
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Cursory cryptic rescind euphoria
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Lucubrate ruffian
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Indigence umbrage
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Emaciate valiant tractable
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Volatile fission cajole
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Concord legacy chisel fagged
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Egress reconcile contrite cred...
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Abstruse salacious constrict
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Unearth recreancy paucity
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                A meeting #1
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                A meeting #2
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Assuage foppish
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Clamor austere collusion
SUBMIT   STORE... Alan.Reid@exchangeserverpro.net   {}                                Waffle saturnine

...snip!
So in the case where I want to search a broader time window, but see fewer irrelevant results, I can combine the -Sender and -Recipients parameters in my search command.

Searching Message Tracking Logs by Recipient Email Address

It doesn’t matter whether the recipient was in the To, CC, or BCC of the message, the search will return any match regardless. Here the “Payroll report for September” email shown above is found even though Alex Heyne was one of several recipients and was in the CC field.
[PS] C:\>Get-MessageTrackingLog -Sender Alan.Reid@exchangeserverpro.net -Recipients alex.heyne@exchangeserverpro.net

EventId  Source   Sender                            Recipients                        MessageSubject
-------  ------   ------                            ----------                        --------------
RECEIVE  SMTP     Alan.Reid@exchangeserverpro.net   {David.Gower@exchangeserverpro... Payroll report for September
DELIVER  STORE... Alan.Reid@exchangeserverpro.net   {Alex.Heyne@exchangeserverpro.... Payroll report for September
You can specify multiple recipient SMTP addresses simply by separating them with a comma. When you do this the condition is an “or” not an “and”. In other words, any messages with any one of the recipients will be returned in the results, they do not need to be messages sent to all the recipients.
Here both the payroll email sent to Alex and David, as well as another email sent only to David, are returned in the same results.
[PS] C:\>Get-MessageTrackingLog -Sender Alan.Reid@exchangeserverpro.net -Recipients alex.heyne@exchangeserverpro.net,david.gower@exchangeserverpro.net

EventId  Source   Sender                            Recipients                        MessageSubject
-------  ------   ------                            ----------                        --------------
RECEIVE  SMTP     Alan.Reid@exchangeserverpro.net   {David.Gower@exchangeserverpro... Payroll report for September
DELIVER  STORE... Alan.Reid@exchangeserverpro.net   {Alex.Heyne@exchangeserverpro.... Payroll report for September
DELIVER  STORE... Alan.Reid@exchangeserverpro.net   {David.Gower@exchangeserverpro... Payroll report for September
RECEIVE  SMTP     Alan.Reid@exchangeserverpro.net   {David.Gower@exchangeserverpro... Also how about lunch?
DELIVER  STORE... Alan.Reid@exchangeserverpro.net   {David.Gower@exchangeserverpro... Also how about lunch?

Searching Message Tracking Logs for Wildcard Values or Partial Matches

Unfortunately wildcard searches are not allowed with the -Sender and -Recipient parameters.
For example, this will return no results.
[PS] C:\>Get-MessageTrackingLog -Recipients *@gmail.com
However, you can use wildcards if you pipe the output of Get-MessageTrackingLog into Where-Object instead.
In this situation it is wise to limit the search to a specific date range for better performance. Or, if you do need to search the entire set of log files remember to use “-Resultsize Unlimited”.
[PS] C:\>Get-MessageTrackingLog -Start (Get-Date).AddHours(-1) | Where-Object {$_.recipients -like "*@gmail.com"}

EventId  Source   Sender                            Recipients                        MessageSubject
-------  ------   ------                            ----------                        --------------
RECEIVE  STORE... Alan.Reid@exchangeserverpro.net   {exchangeserverpro@gmail.com}     Email to the internet!
TRANSFER ROUTING  Alan.Reid@exchangeserverpro.net   {exchangeserverpro@gmail.com}     Email to the internet!
SEND     SMTP     Alan.Reid@exchangeserverpro.net   {exchangeserverpro@gmail.com}     Email to the internet!
You can see that the wildcard is used with the -like comparison operator, but another technique is to use the -match comparison operator which doesn’t require the wildcard character.
[PS] C:\>Get-MessageTrackingLog -Start (Get-Date).AddHours(-1) | Where-Object {$_.recipients -match "gmail"}

EventId  Source   Sender                            Recipients                        MessageSubject
-------  ------   ------                            ----------                        --------------
RECEIVE  STORE... Alan.Reid@exchangeserverpro.net   {exchangeserverpro@gmail.com}     Email to the internet!
TRANSFER ROUTING  Alan.Reid@exchangeserverpro.net   {exchangeserverpro@gmail.com}     Email to the internet!
SEND     SMTP     Alan.Reid@exchangeserverpro.net   {exchangeserverpro@gmail.com}     Email to the internet!
The same use of Where-Object with -like or -match also applies to the sender email address


Source : http://exchangeserverpro.com/searching-message-tracking-logs-by-sender-or-recipient-email-address/

Kamis, 10 September 2015

"Unable to Create System DSN" ketika membuka program eSPT

Untuk pc yang terhubung ke domain server, dan login user yang memiliki batasan hak akses, terdapat beberapa masalah jika menggunakan program database / Data Sources (ODBC), karena database yang kita buat di login administrator ada kala nya tidak bisa di akses jika menggunakan login user.

Salah satunya yaitu program eSPT PPh Masa Pasal 4 ayat (2).
biasa nya program tersebut hanya bisa di jalankan di login administrator karena secara default Data Sources (ODBC) hanya bisa di ubah dalam login administrator.

Jika menggunakan login user (non-administrator) biasanya akan muncul pesan :  "Unable to Create System DSN" ,
Dan jika kita coba buka (ODBC Data Source Administrator)
Opening Administrative Tools -> Data Sources (ODBC) -> Click "System DSN" tab.
Maka akan muncul pesan error:
ODBC System DSN Warning You are logged on with non-Administrative privileges.
System DSNs could not be created or modified.

Untuk solusi nya yaitu, masuk ke login administrator
buka : regedit - HKEY_LOCAL_MACHINE  - SOFTWARE - ODBC
klik kanan di ODBC pilih Permissions, tambahkan login user dan permission yang diperbolehkan untuk mengakses Database tersebut.

Selasai, sekarang login user anda (domain user) dapat membuka program pajak tersebut.


source : http://idtechnical.blogspot.co.id/2013/03/unable-to-create-system-dsn-ketika.html

Rabu, 09 September 2015

How to Fix "You've been signed in with a temporary profile" Error in Windows 8 and 8.1





 
 
How to read event log details for User Profile Service error:

  • Open Event Viewer (eventvwr.msc), then expand open Windows Logs and Application in the left pane.
  • Right click or press and hold on Application in left pane, click on Find, type 1511 (for Event ID), and click/tap on Find Next.
  • Close the Find dialog, and view details. Repeat to view any other listed 1511 Event IDs if needed.


Click image for larger version

Click image for larger version


EXAMPLE: "You've been signed in with a temporary profile" Notification Message

Name:  You've_been_signed_in_with_a_temporary_profile.jpg
Views: 274934
Size:  39.5 KB



Here's How:

1. If you have another administrator account that is not affected by this user profile error, then sign out of the affected account (ex: Brink), and sign in to the other administrator account.

Note   Note
If you do not have another administrator account to sign in to, then you could do one of the following options below to enable the built-in Administrator account to sign in to, and continue on to step 2 below.

A) If the affected account is an administrator, then enable the built-in Administrator account, sign out, and sign in to Administrator.

OR

B) Boot into safe mode, enable the built-in Administrator, sign out, and sign in to Administrator.


2. Back up anything that you do not want to lose in the C:\Users\(user-name) profile folder (ex: Brink) of the affected user account to another location. When finished, delete the C:\Users\(user-name) folder.

3. Press the + R keys to open the Run dialog, type regedit, and click/tap on OK.

4. If prompted by UAC, then click/tap on Yes.

5. In Registry Editor, navigate to the location below. (see screenshot below)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList


Click image for larger version

6. In the left pane under ProfileList, click on a SID key (S-1-5-21....long number). (see screenshot above)
NOTE: Usually, it will be for the SID key that has .bak at the end of the long number.

A) In the right pane of the SID key, look at the ProfileImagePath value to see if it is for the same user account name (ex: Brink) that has the user profile error.

B) If not, then repeat step 6 until your find it, then go to step 7 below.

7. Right click or press and hold on the SID key (ex: ...-1006.bak) found in step 6, and click/tap on Delete. (see screenshot below step 5)

8. Click/tap on Yes to confirm. (see screenshot below)

Name:  ProfileList_Registry-2.jpg
Views: 248548
Size:  21.0 KB

9. If there is another SID key (ex: ...-1006 at end) with the exact same long number from step 6 for the same user account (ex: Brink) without .bak at the end of it, then repeat step 7 and 8 above for it as well.

Name:  Two_SIDs.jpg
Views: 248542
Size:  10.4 KB

10. When finished, close Registry Editor.

11. See if you are now able to sign in to the user account (ex: Brink) from step 1 without getting the "You've been signed in with a temporary profile" error.

12. If successful, the affected account's (ex: Brink) user profile will be recreated and no longer receives the error. You can then copy any files you want back from the back up created at step 2.





source: http://www.eightforums.com/tutorials/38817-youve-been-signed-temporary-profile-fix.html