Skip to main content

Correction to a Lecture: Outlook Voting Buttons

On occasion, I do discover a mistake that I made in class. Below is part of the long list of Questions and Answers I sent to Indiana State University following my presentation of Outlook Power User. I keep track of all questions that my students ask, in regards to the material, that we cannot answer in class and I email them the results of my research.


I found a portion of the lecture that I skipped over concerning voting buttons. While reviewing the voting button setting in Technet to discover if it is possible to receive the result over Outlook Anywhere, I found that I skipped a step. Below is the complete procedure from creating the email to viewing the results.

1. Start by creating a new e-mail.
2. Address the email and give it the subject and body that you want to use.
3. Click the Options tab
4. Click Use Voting Buttons.
5. You can use the present voting options or click Custom.
6. You have the option of clicking Save Sent Item and telling Outlook to use another folder or to use the Default Folder which will place the message in your Sent Items folder.
7. Send the message.
8. Once you have responses, go to Sent Items (Or whatever folder you saved the message to).
9. Open the original email that you sent.
10. In the upper left hand corner in the Show area, click Tracking. This will show you the results.

• For your users to vote.
o When they receive the message, have them look in the upper left hand corner of the window in the Respond section.
o Click Vote and select the their option.

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...