MSCONFIG:
Select the “Boot” tab and uncheck safe boot:
IT Services | IT Consulting | Computer Repair | Computer Services | Computer Network | Business computer
MSCONFIG:
Select the “Boot” tab and uncheck safe boot:
Outlook 2007 did away with the export account information that was present in earlier editions. So, if a user with one account moves machines, it’s often faster to just recreate the account on the new machine. However, if a user has 8 accounts (like one did today) it’s time to find a better way.
That better way is hidden the registry.
Outlook 2007 is nice enough to put all of its account info for each profile under one key.
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\
So, first off, close Outlook if it’s running.
To export your Outlook account information, we just need to export that magic key.
Caveats: Every profile on your system under your logon will be exported.
To move your old mail, you’ll need to copy your PST file to the new machine.
First, we need to import the profile information.
Next, we need to get your data file back over.
Lastly, we need to set Outlook to use the profile from the old machine.
Now, when you open Outlook, you should have your old mail and the mail accounts all set up and ready to go.
Outlook on the new machine mightwill ask you for passwords the first time it does a send/receive on all non-Exchange accounts.
If you know the passwords, awesome. If not, you’ll need to find them out, and we go back to the old machine to do so.
What we need to do is peer behind the dots that Microsoft uses in their password boxes. To do so, we need a piece of freeware that will do that for us.
Passware offers a utility, Asterisk Key, which will do the job.
This article provides instructions for installing ESXi on a USB drive or SD flash card. However, certain considerations must be made before proceeding with an installation. Ensure that the USB flash drive or SD flash card you are using is supported for installation of ESXi 5.x, consult your server vendor for the appropriate choice of a USB or SD flash storage device.
Note: In the event that your original SD flash card or USB drive fails, these steps can be used in a disaster recovery capacity to get a fully functional ESXi host running as quickly as possible on a replacement USB drive or SD flash card.
Note: Installing ESXi 5.x on a USB flash drive or SD flash card has the same minimum requirements as installing to typical SCSI or SATA hard disk. For more information, see the minimum requirements in our vSphere 5.x Documentation Center and ESXi Hardware Requirements.
When installing ESXi onto a USB flash drive or SD flash card, if the drive is less that 8GB is space, this prevents the allocation of a scratch partition onto the flash device. VMware recommends using a retail purchased USB flash drive of 16GB or larger so that the “extra” flash cells can prolong the life of the boot media but high quality parts of 4GB or larger are sufficient to hold the extended coredump partition.To workaround this limitation:
If you have a local datastore containing production information and have completed the installation on a replacement USB flash drive or SD flash card in a disaster recovery scenario, you may be required perform these additional steps:
http://support.microsoft.com/kb/299875/en-us
This article was previously published under Q299875
The following items describe the recommended hardware, software, network infrastructure, skills and knowledge, and service packs that you will need:
If the computer that is hosting Certificate Server is not the same computer that has IIS, you need a valid network or Internet connection to the server that is hosting Certificate Server.
First, the Web server must make a certificate request. To do this, follow these steps:
Note If you type anything other than the default location and file name, be sure to note the name and location you choose, because you will have to access this file in later steps.
The certificate request that you just created needs to be submitted to a Certificate Authority (CA). This may be your own server with Certificate Server 2.0 installed on it or an online CA such as VeriSign. Contact the certificate provider of your choice and determine the best level of certificate for your needs. There are different methods of submitting your request. Contact the Certificate Authority of your choice to request and receive your certificate. You can create your own certificate with Certificate Server 2.0, but your clients must implicitly trust you as the Certificate Authority. The steps below assume that you are using Certificate Server 2.0 as the certificate provider.
Note The IIS Certificate Wizard will only recognize the Default Web Server template. When you select an Online Enterprise CA, the Authority will not be listed unless the CA is using the Default Web Server template.
-----BEGIN NEW CERTIFICATE REQUEST----- MIICcjCCAhwCAQAwYjETMBEGA1UEAxMKcm9ic3NlcnZlcjELMAkGA1UECxMCTVMx CzAJBgNVBAoTAk1TMREwDwYDVQQHEwhCZWxsZXZ1ZTERMA8GA1UECBMIV2FzaGl0 b24xCzAJBgNVBAYTAlVTMFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALYK4sYDNQ7h LmSfL0qpIvUfY7Ddw7fNCvDp3rM7z4QqoLhA2c8TkyamqWTBsV0WRHIidf/J6mU4 wN4wrUzJTLUCAwEAAaCCAVMwGgYKKwYBBAGCNw0CAzEMFgo1LjAuMjE5NS4yMDUG CisGAQQBgjcCAQ4xJzAlMA4GA1UdDwEB/wQEAwIE8DATBgNVHSUEDDAKBggrBgEF BQcDATCB/QYKKwYBBAGCNw0CAjGB7jCB6wIBAR5aAE0AaQBjAHIAbwBzAG8AZgB0 ACAAUgBTAEEAIABTAEMAaABhAG4AbgBlAGwAIABDAHIAeQBwAHQAbwBnAHIAYQBw AGgAaQBjACAAUAByAG8AdgBpAGQAZQByA4GJAGKa0jzBn8fkxScrWsdnU2eUJOMU K5Ms87Q+fjP1/pWN3PJnH7x8MBc5isFCjww6YnIjD8c3OfYfjkmWc048ZuGoH7Zo D6YNfv/SfAvQmr90eGmKOFFiTD+hl1hM08gu2oxFU7mCvfTQ/2IbXP7KYFGEqaJ6 wn0Z5yLOByPqblQZAAAAAAAAAAAwDQYJKoZIhvcNAQEFBQADQQCgRCWkaXlY2nVa tbn6p5miPwWfrbViYo0B62wkuH0f7J0nSGcxMnn/6Q/iLEIsgHqFhox5PWCzIV0J tXKPWrBL -----END NEW CERTIFICATE REQUEST-------
Note If you save the document with the default name and location, it is located at C:\Certreq.txt.
Note Be sure to copy all of the content just as shown.
To issue a certificate in Certificate Server, follow these steps:
Note After you select Issue, the certificate is no longer displayed in this window and folder. It now resides in the Issued Certificate folder.
To install the certificate, follow these steps:
To configure and test the certificate, follow these steps:
HTTP 403.4 – Forbidden: SSL required.
150031 Use of SSL creates performance overhead for browsers
238662 Using Visual InterDev and Secure Sockets Layer
cmd:
netsh int ip reset c:\resetlog.txt
netsh winsock reset
Start gpedit.msc
Go to:
Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon
http://support.microsoft.com/kb/305293
By default in Windows 8, Windows 7, Windows Vista, and Windows XP, the Fast Logon Optimization feature is set for domain and workgroup members. Policy settings apply asynchronously when the computer starts and when the user signs in. As a result, Windows 8, Windows 7, Windows Vista, and Windows XP do not wait for the network to be fully initialized at startup and sign-in. Existing users are logged on by using cached credentials. This results in shorter logon times. Group Policy is applied in the background after the network becomes available. Be aware that, because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logons to apply changes. Additionally, changes that are made to the user object, such as adding a roaming profile path, root directory, or user object logon script, may take two logons to be detected.
If you turn off this feature, Windows waits for the network to be fully initialized before users are logged on. This results in the synchronous application of policies when the computer starts and when the user logs on. This application of policies resembles a background refresh process and can reduce the time that is required for the Logon dialog box to display and the time that is required for the shell to be available to the user. An administrator can change the default by using the Group Policy MMC snap-in.
Fast Logon Optimization is always off during logon when a user first logs on to a computer.
You should be aware that, under the previous conditions, computer startup can still be asynchronous. However, because logon is synchronous under these conditions, logon does not exhibit optimization.
When your folder redirection policy is not completely applied at first logon, you can find the following warning in the event log:
Event Type: Warning
Event Source: Folder Redirection
Event Category: None
Event ID: 301
Description: Folder redirection policy application has been delayed until the next logon because the group policy logon optimization is in effect.
Be aware that when logon optimization is turned on, a user may have to log on to a computer two times before folder redirection policies and software installation policies are applied. This is because applying these kinds of policies requires the synchronous policy application. During a policy refresh (which is asynchronous), the system sets a flag that indicates that applying folder redirection or a software installation policy is required. The flag forces synchronous application of the policy at the user’s next logon.
BE aware that Windows clients support Fast Logon Optimization in any domain environment. To turn off Fast Logon Optimization, you can use the following policy setting:
Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon
When this policy is enabled, a Windows XP client behaves in the same manner as a Windows 2000 client at both system startup and at user logon.
Note This also applies to systems that are running Windows 7 or Windows 8. However, in those systems, the event ID changes to 510:
Event Log: Application Log
Event Type: Error
Event Source: Microsoft-Windows-Folder Redirection
Event ID: 510
Description: Folder redirection policy application has been delayed until the next logon because the group policy logon optimization is in effect.
This article provides instructions for detecting .NET Framework versions on a computer both manually and programmatically, and detecting the runtime version using a tool and programmatically. For information about detecting the installed updates for each version of the .NET Framework, see How to: Determine Which .NET Framework Updates Are Installed. For information about installing the .NET Framework, see the installation guide.
You must have administrative credentials to run regedit.exe.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP
The installed versions are listed under the NDP subkey. The version number is stored in the Version entry. For the .NET Framework 4 the Version entry is under the Client or Full subkey (under NDP), or under both subkeys.
Note |
---|
The “NET Framework Setup” folder in the registry does not begin with a period. |
You must have administrative credentials to run regedit.exe.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
Check for a DWORD value named Release. The existence of the Release DWORD indicates that the .NET Framework 4.5 or newer has been installed on that computer.
The value of the Release DWORD indicates which version of the .NET Framework is installed.
Version | Value of the Release DWORD |
---|---|
.NET Framework 4.5 | 378389 |
.NET Framework 4.5.1 RC | 378681 |
From a Visual Studio Command Prompt enter clrver. This command produces output similar to the following.
For more information about using this tool, see Clrver.exe (CLR Version Tool)
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 5603
Description:
A provider, PerfProv, has been registered in the WMI namespace, ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
Resolution:
open WMI (Windows Management Infrastructure): Start > run > wmimgmt.msc
Windows Management Infrastructure (WMI) > WMI Control (local) > Properties
Properties > Security (tab) > Root (tree) > CIMV2 > MicrosoftHealthMonitor > PerfMon > Security (button)
Security for ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon > Security > Add (button) > Advanced > Find now > Performance Log Users (select) > OK
Performance Log Users (select) > Execute Methods (tick) > Enable Account (tick) > Remote Enable (tick)
Start gpedit.msc
Go to:
User Configuration->Administrative Templates->Windows Components->Windows Explorer
enable “Turn off the caching of thumbnails in hidden thumbs.db files”
If you want to speed up browsing around in explorer, you might think about disabling thumbnail previews in folders.
Note that this works in Windows 7 or Vista
To make this change, click the Organize button on any folder, and choose Folder and Search Options from the menu.
Click the View tab, and then check the Always show icons, never thumbnails checkbox.
Your Exchange administrator can automatically configure all copies of Outlook in your organization or provide a special executable script file that enables Outlook Anywhere. You can also manually configure Outlook Anywhere if the system requirements are met and you have the correct URL and security information from your Exchange administrator.
NOTE If the Outlook Anywhere section is not available, your computer is probably not running Windows XP Service Pack 2 or a later service pack.
Type the URL provided by your Exchange administrator.
If your Exchange administrator tells you to use a Secure Sockets Layer (SSL) connection, select the Connect using SSL only check box.
If your Exchange administrator instructs you to do so, select the Only connect to proxy servers that have this principal name in their certificate check box, and then type msstd: followed by the URL provided by the administrator.
NOTE If you click Basic Authentication or NTLM Authentication and an LM Compatibility Level of less than 2, you will be prompted for a password each time a connection is made to Exchange. With Basic Authentication, the password is sent in clear text. For increased security, we recommend that you select theNTLM Authentication and Connect using SSL only options.