IMAGE FAILED TO VERIFY WITH access denied X240 ERROR

Problem solved. I had to disable secure boot in the bios security tab

networking stoping while sleep mode windows 7

Navigate to the control panel and open the Device Manager. Open the Network adapters section, right-click your wifi adapter and choose Properties. Navigate to the Power Management tab, uncheck allow the computer to turn off this device and set it to allow this device to wake the computer and then save the changes you made.

http://www.tomshardware.com/forum/48676-63-wifi-turns-sleep-mode

 

"From" Lync Presence Not Appearing in Outlook 2013

I was experiencing the same behaviour - We have Exchange 2010, Outlook 2013, Lync 2010.  Lync repair did not work.

Fix:  Delete/Re Create Outlook Account

1. Close outlook
2. Open Control Panel > Mail > Email Accounts
3. Delete the default profile
4. Create a new profile - Manually
5. Set offline slider to "All" (all the way to the right)
6. Start Outlook
7. Bingo

http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/from-lync-presence-not-appearing-in-outlook-2013/f3435832-9e7e-4d4b-b65e-c0f0b67570e3?page=2 

tcp window size

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ interface-name

Data type	Range	Default value
REG_DWORD	0x0–0x3FFFFFFF ( bytes )	(See description.)

Description
Determines the largest TCP receive window that the system offers. The receive window is the number of bytes a sender can transmit without receiving an acknowledgment. This entry overrides TCP's negotiated maximum receive window size and replaces it with the value of this entry.
TCP uses a receive window that is four times the size of the maximum TCP segment size (MSS) negotiated during connection setup, up to a maximum size of 64 KB. TCP for Windows 2000 also supports windows scaling, as detailed in RFC 1323, TCP Extensions for High Performance. Scaling enables TCP to provide a receive window of up to 1 GB.
For Ethernet networks, the default value of this entry is 0x4470 (17,520, or 12 segments of 1,460 bytes each). For other networks, the default value is 0xFFFF (65,535) unless 0xFFFF is larger than:

• Four times the maximum TCP data size on the network; and
• 0x2000 (8,192) rounded up to an even multiple of the network TCP data size.

Note
This entry determines the maximum receive window size for this interface. When configuring this interface, this entry takes precedence over the GlobalMaxTcpWindowSize entry, which establishes a maximum window size for all interfaces.
Windows 2000 automatically uses windows scaling if the value of this entry is greater than 64 KB. To disable windows scaling, set the value of the Tcp1323Opts entry to 0 or 2.
Windows 2000 does not add this entry to the registry. You can add it by editing the registry or by using a program that edits the registry

System File Checker: Run sfc /scannow & Analyze its logs in Windows 7 | 8

he System File Checker or sfc.exe is a utility in Microsoft Windows located in C:\Windows\System32 folder. This utility allows users to scan for and restore corrupt Windows system files.

System File Checker

In Windows 8, Windows 7 & Vista, the System File Checker is integrated with Windows Resource Protection, which protects registry keys and folders as well as critical system files. If any changes are detected to a protected system file, the modified file is restored from a cached copy located in the Windows folder itself.

So if at any point of time if you find that you have hacked some system files or maybe applied some tweaks or replaced system files, maybe while customizing your Windows, and you now find that your Windows is not working properly, you may want to consider running this utility first, before trying a System Restore. To do so, you will have to first open anelevated command prompt window.

To run the System File Checker in Windows 8, Windows 7 or Windows Vista, type cmd in start search box. In the result, which appear, right click on cmd and select Run As Administrator.

Run sfc /scannow

In the command prompt window which opens, type sfc /scannow and hit Enter.

The sfc utility will run for a while and if any corruptions are found, replace them on re-boot.

In case you are unable to start the System File Checker and you instead get the “Windows Resource Protection Could Not Start the Repair Service” error, you may want to check up if your Windows Modules Installer service has been Disabled. To do so, type services.msc in start search and hit Enter. The status of this services should be set to Manual. Alternatively, you can also download our very useful freeware utility FixWin and click on the System File Checker Utilitybutton. This will run sfc.exe.

Some more sfc switches:

Scan once at next boot:   sfc /scanonce
Scan at every boot:  sfc /scanboot
Purge File Cache:  sfc /purgecache
Return to Default Setting:  sfc /revert

You can also use the sfc.exe program to help you troubleshoot crashes that occur in the user mode part of Windows 7 & Vista. These crashes may be related to missing or damaged operating system files. To do so you may have to access the log files.

How to view the log file.

The sfc.exe program writes the details of each verification operation and of each repair operation to the CBS.log file. Each sfc.exe program entry in this file has an [SR] tag. The CBS.log file is located in the %windir%\Logs\CBS folder.

You can search for [SR] tags to help locate SFC.exe program entries. To perform this kind of search and to redirect the results to a text file, follow these steps:

Click Start, type cmd in the Start Search box, right-click cmd in the Programs list, and then click Run as administrator.

Type the following command, and hit Enter:

findstr /c:”[SR]” %windir%\logs\cbs\cbs.log >sfcdetails.txt

The sfcdetails.txt file includes the entries that are logged every time that the SFC.exe program runs on the computer.

How to interpret the log file entries:

The sfc.exe program verifies files in groups of 100. Therefore, there will be many groups of SFC.exe program entries. Each entry has the following format: date time entry_type details. For more details on how to interpret, visit KB928228.

Go here if you find that System File Checker (SFC) cannot repair corrupted member file.

http://www.thewindowsclub.com/how-to-run-system-file-checker-analyze-its-logs-in-windows-7-vista 

How to enable ROOT password in Ubuntu 12.0.4

1. Open a terminal

2. Type sudo passwd -u root

(This is enable root account password expiry time)

3. Type passwd root

(This command is for changing the ROOT password)

4. Please enter the password as required by you

5. Again enter the password as the same entered first time.

6. Type su

(Now it would ask for ROOT password give your password and enter into ROOT.

Cannot add to the server Junk E-mail Lists, you are over the size allowed on the server. The Junk E-mail Filter on the server will be disabled until your Junk E-mail Lists have been reduced to the size allowed by the server

Microsoft Exchange has a limit to the size of the rule where your different "junk" lists are stored. By default, the limit is 510 KB.

In relation to this limit, there are four known causes for the above errors.

• You have a large number of entries in your Safe Senders, Blocked Senders, and Safe Recipients lists
  
  By default, you have a cumulative limit of 510 KB for all of your junk e-mail lists. If you have a large number of entries in these lists (cumulatively), then you may receive the above error when you attempt to add more items to the lists.
• The Max Extended Rule Size registry value is incorrectly configured on the Exchange server
  
  On an Exchange server, you can configure the following registry data:
  
  Registry key: HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
  Value: Max Extended Rule Size
  Type: DWORD
  Data: an integer specifying the maximum size, in bytes, you want to allow for the junk e-mail rule
  
  The value you enter in the registry is interpreted as the maximum rule size in bytes. Therefore, if you want to specify a limit that is higher than the default 510 KB, you need to enter a value higher than 522240 (decimal).
  
  The above error can occur when you inadvertently specify a value lower than the default limt. For example, you enter a value of 1024 under the assumption that this is doubling the default limit of 510 KB. Since the value you enter is interpreted as a number of bytes, a value of 1024 means you have configured a limit of 1024 bytes, substantially lower than the default limit of 510 KB.
• The PR_RULE_MSG_STATE property of the Junk E-mail Rule message is incorrectly configured
  
  With an Exchange mailbox, your junk e-mail settings are stored in a hidden message in the associated contents table of your Inbox folder. The subject of this hidden message is Junk E-mail Rule. This message has a property calledPR_RULE_MSG_STATE and the default value on this property is 49 (decimal) or 0x31 (hexadecimal). If you then disable junk email filtering in Outlook Web App, the value of this property becomes 48 (decimal) or 0x30 (hexadecimal). Therefore, if the value specified on this property is something other than 48 or 49 (decimal), then you may receive the above error.
• The "Also trust e-mail from my Contacts" option is enabled in Outlook
  
  On the Safe Senders tab of the Junk E-mail Options dialog box you can configure the Also trust e-mail from my Contacts option. If enabled, and you have a large number of contacts in your Contacts folder, you may inadvertently exceed the 510 KB limit on your mailbox. With this option enabled, Outlook attempts to add all of the email addresses for your contacts to the Safe Senders list. 

http://support.microsoft.com/kb/2669081 

Setup and Configure SMTP Server on Windows Server 2008 R2

There has been some confusion about how to setup and configure SMTP onWindows Server 2008 R2. The confusion has arisen due to the SMTP server component not being managed from with IIS 7.5 but is instead managed from theIIS 6 console.  In order to have SMTP working you must install IIS 6 as a feature. The following steps will explain how to setup and configure SMTP from start to finish.

Installing the SMTP feature

1. Click Start > Run and then enter servermanager.msc in the Open dialogue box then click OK to load Server Manager:

C:\>servermanager.msc

2. Use the Add Features Wizard to select SMTP Server on the Select Features page. To initiate this, right-click on Features and click Add Feature:

3. In the Features section check SMTP Server and click Next:

4. You may see a dialogue box like the one below stating that certain role services and features are required for SMTP:

5. Click Add Required Role Services and then you will return to the previousFeatures section. Ensure SMTP Server is checked then click Next.

6. In the Web Server (IIS) section, click Next to proceed to the Role Servicessection:

7. The Role Services should be pre-populated – IIS 6 Management Compatibility should be selected, and below it, IIS 6 Metabase Compatibilityand IIS 6 Management Console should also be checked. Click Next to continue:

8. In the Confirmation section click Install:

9. In the Results section click Close to complete the installation of the SMTP Server:

Configuring the SMTP Server

The next step is to configure SMTP. To do so we will need to open Internet Information Services (IIS) Manager 6.

10. Click Start > Run and then enter inetmgr6 in the dialogue box then click OKto load IIS Manager 6.

11. In IIS 6 Manager right-click on SMTP Server and select Properties:

12. In the General tab, unless you want the SMTP Server to use a specific IP address,  leave the settings as they are so that the IP address is set to (All Unassigned):

13. To proceed, click on the Access tab:

14. Click on the Authentication button and ensure Anonymous access is checked and then click OK:

15. Once back in the Access tab, click on the Connection button. Select Only the list below and then click Add. Enter 127.0.0.1 as the IP addess and then click OK:

The Connection setting controls which computers can connect to the SMTP server and send mail. By granting only localhost (127.0.0.1) access, limits only the server itself the ability to connect to the SMTP server. This is a requirement for security.

16. Click OK to return to the Access tab and then click on the Relaybutton. Enter 127.0.0.1 as the IP addess and then click OK:

The Relay section determines which computers can relay mail through this SMTP server. By only allowing the localhost IP address (127.0.0.1) relay permissions it means that only the server itself can relay mail. Conversely, it prevents the SMTP server from being an open relay and being used to send unsolicited spam email by other computers on the internet, which could lead to the SMTP server being blacklisted.

17. Next, go to the Messages tab. Here you can enter an email address where copies of non-delivery reports are sent to. You can also configure the location of the Badmail director, however, the default setting should suffice:

18. Next, go to the Delivery tab:

19. Click on the Outbound Security button and ensure Anonymous access is selected. As the only server that can connect and relay mail through the SMTP server is localhost this security settings is fine:

20. Click OK to return to the Delivery tab and then click on Outbound Connections. Leave the defaults as they are:

21. Click OK to return to the Delivery tab and then click on Outbound Connections, then click on the Advanced button:

Here you will need to enter the fully-qualified domain name of the SMTP server. This will be the host name or A record that has been created in your DNS zone file. This is straight-forward to do but you will have to confirm how you do this with the party that manages DNS for your domain. I have entered mail.vsysad.comas this is fully-qualified. If you click on the Check DNS button you can confirm whether your chosen name resolves successfully. In my case it does as I see the following:

 22. Click OK and then OK again to exit the SMTP Virtual Server Properties.

You can also perform this test by running nslookup to confirm the existence of the host name as well as confirming the IP address it resolves to – which should the IP address of your server:

Testing the SMTP Server

The next step is to verify that the SMTP server is able to send email successfully. To do this follow the steps below:

23. Create a text file on your desktop called email.txt and paste the following into it, remembering to change the email address information to reflect your own details:

From: blog@yourdomain.com

To: email@yourdomain.com

Subject: Email test

This is the test body of the email

.

24. Save the changes to email.txt and then copy the file toC:\inetpub\mailroot\Pickup. The SMTP server monitors this folder and when it detects the email.txt file, it will read the contents and send the email to the address in the To: section. This should happen almost immediately.

25. Check the email address the email was sent to and it should arrive shortly – the email was sent to my Gmail account:

An alternative way of doing this is to use a script to perform the same email test. Simply save the code below into a file called email.vbs, remembering to change the email address information to reflect your own details:

Dim sch, cdoConfig, cdoMessage

sch = "http://schemas.microsoft.com/cdo/configuration/"

Set cdoConfig = CreateObject("CDO.Configuration")

With cdoConfig.Fields

.Item(sch & "sendusing") = 1 ' cdoSendUsingPort

.Item(sch & "smtpserver") = "127.0.0.1"

'    .Item(sch & "smtpserverport") = 25

.update

End With

Set cdoMessage = CreateObject("CDO.Message")

With cdoMessage

Set .Configuration = cdoConfig

.From = "blog@yourdomain.com"

.To = "email@yourdomain.com"

.Subject = "Email test"

.TextBody = "This is the test body of the email"

'.AddAttachment "c:\images\myimage.jpg"

.Send

End With

Set cdoMessage = Nothing

Set cdoConfig = Nothing

MsgBox "Email Sent"

Once the file has been saved to the desktop double-click on it and it should automatically send the the email. A message box pops up to confirm that the email was sent:

Note: You can also use telnet and PowerShell to test mail sending/routing via SMTP Server. Please refer to this post to see how to do this.

That’s all there is to it! Now you have a fully functioning STMP server that can successfully send emails. Many of the companies that I have worked with use this method to send emails generated by their web applications.

Troubleshooting

DNS

It is essential to have DNS setup and working properly, if not you may experience problems with mail delivery. Follow the instructions in this post which shows you how to verify correct DNS configuration using the SMTPDIAG tool. Ensure that you have a PTR record for reverse DNS lookups configured. The PTR record allows your SMTP server’s public IP address to be resolved back to your hostname. Some of the major email hosts use this technique to block spammers. Your web host should have a control panel that allows you to configure reverse DNS if you have a dedicated public IP address. Rackspace Cloud users can follow this link for instructions on how to create a reverse DNS record.

SMTP Folders

If emails are not being successfully delivered you may notice that messages are building up in specific SMTP folders. These are likely to be, but not limited to, Badmail & Queue. Please visit this post to understand the purpose of each SMTP folder and how to approach issues when messages are queuing up in those folders.

http://www.vsysad.com/2012/04/setup-and-configure-smtp-server-on-windows-server-2008-r2/