Instead i created a script that would check the OS Version and see if the update was already installed.

1. First we hide the script from users:
   

   @ECHO Off

2. Then we check they are running the correct OS (for windows 7 “Version 6.1″)
   

   ver | find "Windows XP" >NUL
   if errorlevel 1 goto end

3. Check to see if the update is installed (chance the reg location depending on the install)
   

   reg QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP20\KB943729" >NUL 2>NUL
   if errorlevel 1 goto install_update
   goto end

4. Then if it is the correct OS and the update isn’t installed run the exe
   

   :install_update
   \\PUT_YOUR_SHARE_PATH_HERE\Windows-KB943729-x86-ENU.exe /passive /norestart

5. End (this is added so that the script will stop if the criteria are not met before the update is installed stopping errors.
   

   :end

6. you can then add this to a group policy to allow it to be deployed

Unexpected Exchange mailbox Server error: Server: [server.domain] User: [useremail] HTTP status code: [503]. Verify that the Exchange mailbox Server is working correctly.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This is how i fixed the issue:

1. Open IIS
2. Right click Default-Website
3. Click Properties
4. Click advanced
5. Review sites. most likely you will see host headers and ip address.
6. Click add
7. IP address = (all unassigned)
8. TCP Port = 80
9. Host Header Value = (Blank)
10. Click OK
11. delete the entry with the host headers and ip address assignerd.

This should resolve the issue please comment if you have any issues doing this.

You basically need to create an smtp relay on a local server / computer to forward your scans to then set the smtp relay up as below which will then do the authentication part for you.

SMTP relay settings for Office 365

To configure an SMTP relay in Office 365, you need the following:

• A user who has an Exchange Online mailbox
• The SMTP set to port 587
• Transport Layer Security (TLS) encryption enabled
• The mailbox server name

To obtain SMTP settings information, follow these steps:

1. Sign in to Outlook Web App.
2. Click Options, and then click See All Options.
3. Click Account, click My Account, and then in the Account Information area, click Settings for POP, IMAP, and SMTP access.

   Note the SMTP settings information that is displayed on this page.

Configure Internet Information Services (IIS)

To configure Internet Information Services (IIS) so that your LOB programs can use the SMTP relay, follow these steps:

1. Create a user who has an Exchange Online mailbox. To do this, use one of the following methods:
   • Create the user in Active Directory Domain Services, run directory synchronization, and then activate the user by using an Exchange Online license.

     Note The user must not have an on-premises mailbox.

   • Create the user by using the Office 365 portal or by using Microsoft Online Services PowerShell Module, and then assign the user an Exchange Online license.
2. Configure the IIS SMTP relay server. To do this, follow these steps:
   1. Install IIS on an internal server. During the installation, select the option to install the SMTP components.
   2. In Internet Information Services (IIS) Manager, expand the Default SMTP Virtual Server, and then click Domains.
   3. Right-click Domains, click New, click Domain, and then click Remote.
   4. In the Name box, type *.com, and then click Finish.
3. Double-click the domain that you just created.
4. Click to select the Allow incoming mail to be relayed to this domain check box.
5. In the Route domain area, click Forward all mail to smart host, and then in the box, type the mailbox server name.
6. Click Outbound Security, and then configure the following settings:
   1. Click Basic Authentication.
   2. In the User name box, type the user name of the Office 365 mailbox user.
   3. In the Password box, type the password of the Office 365 mailbox user.
   4. Click to select the TLS encryption check box, and then click OK.
7. Right-click the Default SMTP Virtual Server node, and then click Properties.
8. On the Delivery tab, click Outbound Connections.
9. In the TCP Port box, type 587, and then click OK.
10. Click Outbound Security, and then configure the following settings:
    1. Click Basic Authentication.
    2. In the User name box, type the user name of the Office 365 mailbox user.
    3. In the Password box, type the password of the Office 365 mailbox user.
    4. Click to select the TLS encryption check box, and then click OK.
11. On the Access tab, click Authentication, click to select the Anonymous access check box, and then click OK.
12. On the Relay tab, select Only the list below, type the IP addresses of the client computers that will be sending the email messages, and then click OK.

1. Start Active Directory Users and Computers; click Start, point to Programs, point toAdministrative Tools, and then click Active Directory Users and Computers.

2. On the View menu, make sure that Advanced Features is selected.

3. Double-click the user that you want to grant send as rights for, and then click theSecurity tab.

4. Click Add, click the user that you want to give send as rights to, and then check send as under allow in the Permissions area.

4.5  Remove all other permissions granted by default so only the send as permission is granted.

5. Click OK to close the dialog box.

So after I verified that the steps for KB281208 worked, I was curious as to why the steps for KB327000 did not work.  What I found was that Step #7 of KB327000 applied to the permission to “User Objects” instead of “This Object Only”.  Here are the modified steps for KB327000 that I performed:

1. On an Exchange computer, click Start, point to Programs, point to Microsoft Exchange, and then click Active Directory Users and Computers.

2. On the View menu, click to select Advanced Features.

3. Expand Users, right-click the MailboxOwner object where you want to grant the permission, and then click Properties.

4. Click the Security tab, and then click Advanced.

5. In the Access Control Settings for MailboxOwner dialog box, click Add.

6. In the Select User, Computer, or Group dialog box, click the user account or the group that you want to grant “Send as” permissions to, and then click OK.

7. In the Permission Entry for MailboxOwner dialog box, click This Object Only in theApply onto list.

8. In the Permissions list, locate Send As, and then click to select the Allow check box.

9. Click OK three times to close the dialog boxes.

The KB articles were updated to include correct information. But, if you had problems with this in the past, this might be why!

Both tasklist.exe and taskkill,exe can be found in %SYSTEMROOT%\System32 (typically C:\Windows\System32) directory.

To view processes on a remote Computer in your home, you will need to know the username and password on the Computer you want to view the processes. Once you have the user account information, the syntax for using tasklist follows:

tasklist.exe /S SYSTEM /U USERNAME /P PASSWORD

(To view all tasklist options, type tasklist /? at the command prompt)

To execute, click on Start \ Run… and in the run window type cmd to open a command prompt. Then type the tasklist command, substituting SYSTEM for the remote computer you want to view processes, USERNAME and PASSWORD with an account/password on the remote Computer.

(NOTE: if you are in a Domain environment and have Administrator rights to the remote Computer, you will may not need to specify a Username and Password)

I have been setting up a lot of Fortigate’s recently and on my first few had issues with the settings for LDAP i found that it was tricky to remember the correct settings and also typing out the long LDAP Strings can be a bit tricky and cause typo’s.

1. Logon to the fortigate and go to the Users -> Remote -> LDAP (Create New)
2. Fill in a Name for the connector
3. Fill in the IP Address of the server that has LDAP Installed
4. Change the Common Name Identifier to: sAMAccountName
5. Enter the Distinguished Name if your domain was domain.local the distinguished name would be: DC=domain,DC=local
6. Make your Bind Type Regular
7. In the User DN Box you must type the full path to the user e.g. if you user is domain.local/users/service accounts/fortigate you would need the following: CN=fortigate,OU=Service Accounts,OU=Users,OU=MyBusiness,DC=domain,DC=local
8. type the password for your service account

I managed to resolve this issue by copying the licensing db to a different folder and then re-installing terminal services and copying it back.

1. stop Terminal Services Licensing service
2. Copy c:\windows\system32\LServer\TLSLic.edb
3. Paste the db to a different location
4. Uninstall Terminal Services Licensing from add remove components
5. Re-Install Terminal Services Licensing
6. stop Terminal Services Licensing service
7. copy the TLSLic.edb back to c:\windows\system32\LServer\ overwriting the new db that is in there
8. start Terminal Services Licensing service

Now you will notice that TS Licensing is working and all of your licences still work.

NOTE: You CANNOT move this to another server it is registered to that Licensing server!!!

So you can use DLP sensor to detect this title in http request and block this sites. I have tested this on a FortiGate-60B with 4.2.3 version of firmware.

I tried to solve this problem over application control, web content filter and FortiGuard web filter but I didnt find solution here.

header(location:"index.php");

So to get rid of the error that this produces simply change it to any of the below:

ob_start();

//script

header("Location:file.php");

ob_end_flush();

OR

if ($success)
{
echo '<META HTTP-EQUIV="Refresh" Content="0; URL=success.php">';
exit;
}
else
{
echo '<META HTTP-EQUIV="Refresh" Content="0; URL=retry.php">';
exit;
}

OR

printf("<script>location.href='errorpage.html'</script>");

i used the last option as i found this worked best compared to the others with my program however they may all work well for your application

Here is a simple solution to the issue we have been having:

net use I: \\SERVERNAME\SHARENAME /User:DOMAIN\username password

run this at startup or as a logon script and the issue will be no more.