How to Find Vista's Lost, Hidden, or Deleted Recycle Bin How to Find Vista's Lost, Hidden, or Deleted Recycle Bin. It was probably Mr Nobody who deleted your Vista.![]() ![]()
![]() Replace/Delete Protected DLL Files In Windows 7 & Vista. Windows doesn’t allows the user to delete or replace the protected system files that are very essential to run Windows smoothly. Features a wealth of tutorials on various Windows networking related topics such as setting up Windows NT/XP/2000/2003 networks, troubleshooting, connectivity and more. But we can’t follow Windows rule all the time since we need to experiment with various system files in order to change the functionality or the look of Windows. In most of the causes Windows will not boot if you have not replaced the system file neatly or if you have tinkered with system file in an inappropriate way. To avoid all those frustrations we need to know the right steps to a replace a system file. In Windows XP, we used to use a software called Replacer, but it’s not fully compatible with Windows 7 and Vista. Unlike Windows XP, Vista & 7 doesn’t require to disable “Windows File Protection” feature to play with system files. You can start playing with system files by taking ownership of the files in Vista & 7. Follow the below steps to replace any system file with a new one or to modify it. Make sure you follow the instructions before start the adventure. For instance, let’s consider a system protected file labeled Shell. The best way to start the procedure is to backup Windows. I recommend cloning software like Macrium Reflect (Free) or Acronis True Image or Windows 7’s inbuilt image backup feature to create a good backup.* Head to the folder where the file is located. In this case, Shell. C: \Windows\System. Where “C” is your OS (Operating system) drive.* You can simply create a backup of system file by renaming it. But Windows doesn’t allow you to rename a protected file. So, user needs to take Ownership of the file to rename it.* Read my detailed “How to take ownership of a file in Windows 7” to take the ownership of the file (Same method applies to Vista as well). Once you have the ownership of the file, rename the file. For instance, rename Shell. Shell. 32. OLD. dll. Simply click Continue button if you are prompted with security dialog box.* Obviously, the next step is the copy a new file to with the same of the system file to the same folder. Fox example, you need to move/copy a new “Shell. C: \Windows\System. Also note that it should be a valid file. If you have replaced a system file with invalid file means Windows will not boot next time. So make sure that the system file is valid and works fine with the version of your Windows before replacing the file. You can also delete the file once you have the ownership of the system file.
0 Comments
![]() VMware v. Center Converter Standalone Release Notes. VMware v. Center Converter Standalone 4. Through an intuitive wizard- driven interface and a centralized management console, Converter Standalone can quickly and reliably convert multiple local and remote physical machines without any disruptions or downtime. Benefits. Convert physical machines running Windows or Linux operating systems to VMware virtual machines quickly and without any disruption or downtime. Convert third- party image or virtual machine formats such as Parallels Desktop, Symantec Backup Exec System Recovery, Norton Ghost, Acronis, Storage. Craft, Microsoft Virtual Server or Virtual PC, and Microsoft Hyper- V Server virtual machines to VMware virtual machines. Enable centralized management of remote conversions of multiple physical servers or virtual machines simultaneously. ![]() ![]() In this article, I will show how to resize a VMware disk if you didn't make it large enough when it was created. Furthermore, I will show how to resize. VMware virtualizes computing, from the data center to the cloud to mobile devices, to help our customers be more agile, responsive, and profitable. A failed VMware Converter physical-to-virtual migration has numerous sources of potential failure, and even your best-laid plans may not prevent a problem. Download VMware vCenter Converter Standalone and automate and simplify physical to virtual (P2V) machine conversions. Ensure conversion reliability through quiesced snapshots of the guest operating system on the source machine before data migration. Enable non- disruptive conversions through hot cloning, with no source server downtime or reboot. Top of Page. What's New. The VMware v. Center Converter Standalone 4. Support for VMware v. Sphere 4. 1 as source and destination targets. Support for importing powered- off Microsoft Hyper- V R1 and Hyper- V R2 virtual machines. Public API and sample code for submitting and monitoring Converter jobs. Support for importing Windows 7 and Windows 2. R2 sources. Ability to throttle the data transfer from source to destination based on network bandwidth or CPUIPv. Discontinued Support. Support of the following operating systems is discontinued: Support for OVF format is discontinued. Support for VCB image sources is discontinued. Linux installation support is discontinued. ![]() Top of Page. Installation Notes. Users with limited rights cannot install Converter Standalone 4. Windows. You need to log in as an administrator to install Converter Standalone. Top of Page. Platforms. ![]() ![]() You can install VMware Converter Standalone 4. Windows XP Professional (3. Windows Server 2. SP2, R2 (3. 2- bit and 6. Windows Vista (3. Windows Server 2. Windows Server 2. R2 (6. 4- bit)Windows 7 (3. Top of Page. Interoperability. Converter Standalone 4. Physical machine running an operating system noted in Supported Guest Operating Systems. ![]() VMware View Getting Started Get Started with VMware View Get Started with VMware View VMware View Architecture Planning Introduction to VMware View. VMware KB Article Title: Type of Document: Last Modified: System requirements to install a 64-bit guest operating system on a 32-bit host (1003945). Step by step instructions to increase/change the size of virtual disk and partition in VMware. With VMware disk manager and AOMEI Partition Assistant, it is very easy. VMware Desktop products. Workstation 5. x, 6. Fusion 2. x and 3. Player 2. x and 3. Server 2. x. VMware v. Center virtual machines. ![]() Sphere 4. 1v. Sphere 4. ESX 3. 0. ESXi 3. Installable and Embedded. ESX Server 2. 5. x (if Virtual. Center 2. 5 or later manages ESX Server)v. Center Server 2. 5. Third- party backup images and virtual machines. VMware Support News, Alerts, and Announcements. Update sequence for vSphere 6.5 and its compatible VMware products; Resetting the Administrator password in.Microsoft Virtual PC 2. Microsoft Virtual PC 2. Microsoft Virtual Server 2. Microsoft Virtual Server 2. R2 Hyper- V Server virtual machines that run Windows guest operating systems Hyper- V Server virtual machines that run Linux guest operating systems Acronis True Image Echo 9. Acronis True Image 1. Home product)Symantec Backup Exec System Recovery (formerly Live. State Recovery) 6. Live. State Recovery 3. Norton Ghost version 1. Parallels Desktop 2. Storage. Craft Shadow. Protect 2. 0, 2. 5, 3. For conditions and limitations about converting Backup Exec System Recovery, Shadow. Protect, and Consolidated Backup images, see the VMware v. Center Converter Standalone User's Guide. All other source file systems are converted into ext. Top of Page. Prior Releases of Converter Standalone. Features from prior releases of Converter Standalone are described in the release notes for each release. To view release notes for prior releases of Converter Standalone, click one of the following links: Top of Page. Known Issues. The Converter Standalone 4. Top of Page. Installation. You cannot convert Hyper- V Server virtual machines if v. Center Converter 4. Hyper- V Server. When you try to select a source virtual machine from the Hyper- V Server inventory, the following error message appears: Unable to obtain hardware information for the selected machine. This issue is observed if v. Center Converter 4. Hyper- V Server and Converter Standalone installs Converter Standalone 4. As a result, v. Center Converter 4. This is because the boot- code of some systems cannot handle moving of the boot volume or moving the boot volume beyond the 8. GB mark. You must restart machines that run 6. Windows Vista or later before re- installing Converter Standalone 4. If you uninstall Converter Standalone from a 6. Windows Vista, Windows Server 2. Windows 7 machine and do not restart it, a subsequent Converter Standalone installation might fail with the following error message. Error 2. 91. 44. Could not install service Vstor. Mnt. Api 1. 0 Driver (shared). Please reboot and try to install again. Please keep this in mind when using Converter Standalone client to connect to a remote Converter Standalone server as the communication port might differ. If you choose to leave the remote agent on that source and then install Converter Standalone 4. Converter Standalone installer uninstalls that agent without any warning messages. Users with limited rights cannot install Converter Standalone 4. Windows. If you are logged in to Windows as a non- administrator user, the following error message is displayed while the Install. Shield is extracting files for Converter Standalone installation. Unable to save file. C: \WINDOWS\Installer\. The system cannot find the path specified. The error is displayed because limited users do not have the required write permissions. A Save As dialog box appears. Browse to the Temp folder of the current user (for example, C: \Documents and Settings\. The following error appears in the log file. Agent. Install. Failed. To remove VMware Converter 3. Add or Remove Programs. Remote agent installation is unsuccessful when you specify a computer or DNS name with non- ASCII characters in the Conversion wizard. If you use non- ASCII characters to populate the computer or DNS name field when selecting a source in the Conversion wizard, the installation of Converter Standalone agent fails. This issue is observed for VMware Infrastructure virtual machine destinations, when you connect to a destination v. Center Server and select a destination datastore that has non- ASCII characters in its name. If the connection port is different from the one that is being used for the already running conversion task, both tasks fail. The following error message appears in the Task summary tab for the first conversion task: FAILED: A general system error occurred: No connection could be made because the target machine actively refused it. The following error message appears in the Task summary tab for the second conversion task: FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2. 14. The following error message appears when you click Finish on the Ready to complete page: Unable to create virtual machine. The issue is observed because Converter Standalone worker stops responding if you exceed the maximum supported number of simultaneous conversion tasks. One of the following error messages appears in the Converter Standalone server log file: SSLStream. Impl: :BIORead (0. SSL Exception: The SSL handshake timed out. The following error message might appear in the Converter Standalone worker log file: SSLStream. Impl: :BIORead (1. This error message should read as follows: The destination virtual machine name must be shorter than 8. The number of characters you could input for the destination virtual machine name depends on the language you use. For example, if you are using non- ASCII characters in French or German, the limit for your destination virtual machine name might vary between 4. For non- ASCII characters in Japanese or Simplified Chinese, the limit is fixed at 2. You cannot copy running conversion or configuration tasks. If you open the Copy As New wizard for a running configuration or conversion task when the source is a virtual machine or a backup image and you click Next, the wizard displays the error message Unable to obtain hardware information for the selected machine. This means that Converter Standalone does not recognize the file system on those volumes. The destination virtual machine that is created as a result of such a conversion task might fail to start up. Nevertheless, Converter Standalone copies the source volume data to the destination using block- level copying. Converter Standalone does not split the source files into smaller chunks. If the source is larger than the supported file size on the destination, the conversion tasks fails. Conversions of VMware Infrastructure virtual machine sources with 1. ESX destination managed by Virtual. Center 2. 5 fail. If you convert a virtual machine source that resides on an ESX 3. ESX 3. 5 destination managed by Virtual. Center 2. 5, and the source machine has 1. VMDK files, the conversion task fails with the following error message in Converter Standalone logs. FAILED: agent. internal. Nfc. Connection. Fault. Workaround: Convert the source machine to a hosted virtual machine destination, such as Workstation. Convert the resulting virtual machine to the ESX managed by Virtual. Center where you want it to reside. Creating a conversion task to convert a standalone VMware source with a VMDK file greater than 2. GB from a network share that does not support large files, fails. If you select a standalone virtual machine source with VMDK file greater than 2. GB residing on a remote network location that does not support large files (for example, Linux SMB share), the following error message appears in the Converter wizard on clicking Next or View source details. Unable to obtain hardware information for the selected machine. This might lead to data inconsistency on the destination machine if changes are made to the powered- on source virtual machine during conversion. Conversion tasks are completed successfully, but the user cannot monitor their progress. Converter only checks the first IDE disk in such configurations. Deploying Windows XP Service Pack 2 using Software Update Services. Published: August 1. On This Page. Introduction. Key benefits of using SUS to deploy Windows XP SP2. Situation overview. ![]() Factors to consider when using SUS to deploy Windows XP SP2 Overall recommendations. Summary. Introduction. Windows XP Service Pack 2 (SP2) contains major security improvements designed to provide better protection against hackers, viruses, and worms. ![]() ![]() Windows XP SP2 also improves the manageability of the security features in Windows XP and provides more and better information to help users make decisions that may potentially affect their security and privacy. Microsoft strongly urges customers with Windows XP and Windows XP Service Pack 1- based systems to update to Windows XP SP2 as soon as possible. As a best- practice approach to implementing a managed rollout of Windows XP SP2, customers are encouraged to use a corporate update management solution such as Systems Management Server (SMS) 2. Software Update Services (SUS). The following section details considerations for deploying Windows XP SP2 using SUS. Key benefits of using SUS to deploy Windows XP SP2. Allow administrators to control the deployment Windows XP SP2 (as well as other updates) across their Windows systems. Allow customers to safely disable direct Automatic Updates (AU) or Windows Update (WU) access from individual systems, while allowing these systems to get the necessary critical security updates and other administrator- approved updates. SUS will automatically and silently install Windows XP SP2, while installation of Windows XP SP2 via WU or AU requires user or administrator interaction on each system. Dramatically reduces network traffic into the organization, since updates only need to be downloaded to one or a small number of servers within the organization, instead of being downloaded separately to each system requiring the update. More information on SUS is available at www. Situation overview. Because Windows XP SP2 is a relatively large update (approximately 2. MB), SUS administrators need to consider the impact on internal network traffic and on the machine on which the SUS server is running. For the vast majority of SUS implementations, server and network load will not be a concern and SUS administrators will not have to take mitigation actions described below, although it is recommended that the SUS administrator monitor the performance and load on the SUS server when the update is initially approved. Under ideal conditions for a dedicated SUS server, assuming a 1. Mbps server network card capacity with 2. SUS client to download the Windows XP SP2 update from the server. This translates to 2. While this is the theoretical number of clients that can be supported in a 2.
![]() These include: SUS clients contact the server at randomized intervals of between 1. Hence, the client synchronizations are not serialized and it is likely that more than one client will contact the server at the same time, particularly in environments that have a large number of SUS clients. ![]() If the SUS client machine is turned off when it is scheduled to contact the server, it will attempt to contact the SUS server approximately 1. Because many systems would typically be turned on around the beginning of the work day or the start of a work shift, an unusually high number of clients (relative the volume of clients contacting the server through the rest of the day) would attempt to contact the SUS server at this time. Although clients that cannot be serviced by the SUS server because of capacity limitations will attempt to contact the server again after approximately 5 hours, this overload situation will result in slowing down the server and generating additional network overhead. The following section provides guidance to prevent this situation from occurring. Factors to consider when using SUS to deploy Windows XP SP2 Number of Windows XP systems configured to use a SUS server. Client operating systems Latest update or service pack End of mainstream support End of extended support; Windows Vista : Service Pack 2: April 10, 2012.![]() Bandwidth capacity of the SUS server machine’s network card or network connection Whether the SUS server machine is running other services (e. Available network bandwidth for deploying Windows XP SP2 (if this is less than the bandwidth capacity of the SUS server machine) The following guidance is provided for the minimum SUS server configuration – Intel P7. MB RAM and a 1. 00 Mbps network card and network connection, which is dedicated to running the SUS server (no domain controller, etc.) and is on a network where the available bandwidth exceeds the bandwidth capacity of the server’s network card. If your SUS server machines is running additional services or the available network capacity is less than the server network card capacity, you will need to adjust this guidance to reflect your situation. Overall recommendations. There are essentially three options, depending on the number of Windows XP systems to be updated using your SUS server (if you have one or a few SUS servers) and the topology of your SUS implementation (if you have many SUS servers): No action is necessary if you have less than 2. Windows XP machines that need to be updated with Windows XP SP2 per SUS server. Because Windows XP SP2 is a relatively large update (approximately 270 MB), SUS administrators need to consider the impact on internal. ![]() Use the limited- time approval technique described below if you have between 2. Windows XP machines that need to be updated with Windows XP SP2 via the SUS server Implement one of the following bandwidth throttling mechanisms if you need to control the maximum bandwidth used to deploy Windows XP SP2 using SUS: Limit the maximum number of concurrent connections and maximum bandwidth served on SUS IIS server. Limit the maximum bandwidth used by SUS clients to download SUS content by configuring BITS (Background Intelligent Transfer Service) 2. For the first (no action necessary) option, it is recommended that the SUS administrator monitor the server load when the update is first approved and for the first hour of the work day or first work shift after the Windows XP SP2 update has been approved. The limited- time approval technique works by limiting the number of SUS clients that see the Windows XP SP2 update on the list of approved updates when they contact the SUS server on any given day while this technique is in use, thereby controlling the number of clients that are serviced per day and limiting the server load and additional network overhead (retry attempts, etc.). The third set of options works by limiting the bandwidth used by the SUS implementation, thereby controlling the load on the server and the network. Note: Limiting the load on the SUS server or the network via the options described here will result in it taking longer for all the Windows XP systems to be updated, because the bottleneck is the server load. The guidance provided below for each option is based on the same server load assumption, so it should take approximately the same length of time to deploy Windows XP SP2 irrespective of the option implemented. The following table summarizes the options for the various situations: Option. Do nothing. Use the limited- time approval technique. Implement bandwidth throttling using IIS or BITS 2. Windows XP systems per SUS server. Less than 2. 00. 0Between 2. Typically more than 1. SUS server implementation. SUS servers. One or a few. One or a few. Many. Key requirement. None. Daily SUS administrator intervention, until the number of Windows XP systems left to be updated is less than 2. Configuration of IIS or BITS before approving Windows XP SP2 and resetting the configuration, after fewer than 2. Note: If the bottleneck is the SUS server, one option to address the situation is to add one or more SUS servers (most easily implemented behind a load- balanced network). Limited- time approval technique. This technique relies on the SUS administrator to approve and then un- approve the Windows XP SP2 update on the SUS server on a daily basis, until the number of Windows XP systems that have not received the SP2 update is less than 2. Because the update is only approved for a limited time each day, only a subset of the SUS clients contacting the server on a given day will see the update marked as . SUS clients that contact the server outside this time period will not see the SP2 update in the list of approved updates on the SUS server and will therefore not attempt to download it. This also gives the SUS server time to finish servicing the clients that contacted it during the approval window before a new set of clients attempt to download SP2 when it is re- approved the next day. This is a manual but easily implemented mechanism to control the load on the SUS server and requires no additional infrastructure configuration or testing. SUS administrators can use the following formula to calculate the amount of time for which to approve the Windows XP SP2 update on each day. TA = 2. 40. 00 / (NXP – (1. NDE))Where. TA = Amount of time (in hours) the update needs to be marked as . Using this technique, it is estimated that between 1. SUS client machines will get the Windows XP SP2 update per day. You may monitor the SUS server using performance counters or the Task Manager and increase the length of the approval windows if you determine the load on your SUS server is not high. Increasing the length of the approval windows will allow more clients to download Windows XP SP2 on a daily basis and reduce the time required to update all your Windows XP machines, but increasing the windows beyond a certain threshold (which will vary due to unique factors in your environment) will cause server overload and unnecessary network overhead which will result in increasing rather than decreasing the time required to update all your Windows XP machines. How to Enable and Disable Cookies in Internet Explorer 8 (IE8)Choose to Enable or Disable First and Third- Party Cookies in IE8. Here, you have a few choices to make. First- party cookies are those cookies that come directly from the website you are browsing. Typically, these cookies are used for online shopping carts, usernames, and anything else directly related to the site. Third- party cookies are those cookies from other sites. These cookies are typically used to track advertising, collect non- personal data, and other uses not directly related to site you are visiting. Just for the record, as the visitor to the site, you are considered the second party, which is why there are no second- party cookie options. Under each type of cookie (first and third- party) you can choose to either accept cookies without question, block all cookies, or have Internet Explorer 8 prompt you whenever a website wants to place a cookie on your computer. There are some consequences to each of these choices. ![]() Meet the new browser for Windows 10 and learn the basics. Enable and disable cookies that websites use to track your preferences. Cookies are stored on your computer by websites you visit and contain information such as site. This tutorial will show you how to enable or disable auto update for Internet Explorer 10 (IE10) to install new versions automatically. For more information about. Advanced cookies manager for Internet Explorer. Column Name Description Web site : The Web site that use this cookies file. What is a Computer Cookie? What are the different types of Internet Cookies? Learn about First Party, Third Party, Session, Tracking, Persistent Cookies. Accepting cookies blindly brings up some privacy issues. Technically, information about your surfing habits can be recorded with cookies but this is usually done to make your experience with a website more enjoyable, not as a means to identify you personally or market products to you offline. If you prefer to surf completely anonymously, do not choose to accept all cookies. Blocking cookies can be a problem for you especially if you shop online or participate in online communities. Some people like to allow first- party cookies but disallow third- party cookies. ![]() ![]() Typically, this gives you the best of both worlds. You can use websites as the publisher intended you to use them but you will not have to worry about cookies from sources other than the website you are currently viewing. Having IE8 prompt you every time a site wants to put a cookie on your computer can be a nuisance. Cookies are so prevalent on commercial websites that you will be treated to a barrage of prompts every time you visit a new page. Unless you really want to know every time a website wants to put a cookie on your computer and you don’t mind the constant interruptions, use the PROMPT option for first and third- party cookies. One last option you can choose is whether to allow session cookies. ![]() Session cookies are often used to keep track of your immediate website experience. In other words, shopping carts often use session cookies because once you close your browser, there is no longer any need to keep track of anything you did on the site. However, there is not much distinction between a session and a first or third- party cookie. Disallowing first and third- person cookies and then allowing session cookies may work for you depending on which websites you visit. You may need to play with these options to see what works best for you. ![]() ![]() ![]() Select the check box next to Cookies. Select the Preserve. Update for Internet Explorer 8 Compatibility View List for Windows Vista (KB961813). How to Enable Cookies in Your Internet Web Browser. Cookies are small files that websites store on your computer. These allow the website to recognize your computer. ![]() |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |