Microsoft has officially announced and began the public availability of Windows 7 SP1 Beta and Windows Server 2008 R2 SP1 Beta in the Worldwide Partner Conference 2010. Service Pack 1 of Windows 7 and Windows Server 2008 R2 share the same setup and installation can only be applied on a system running the RTM versions of Windows operating systems.
Although SP1 for Windows 7 and Windows Server 2008 is now publicly available, note that Microsoft does not offer this early release of Windows 7 and Windows Server 2008 R2 SP1 Beta for home users, and installation is not supported by Microsoft. However, everyone who wants to download and install the beta version of SP1, can register for TechNet and be available for download.
The official version of Windows Server 2008 R2 SP1 Beta and Windows 7 SP1 Beta is the same version with the leak of Windows Server 2008 R2 and Windows 7 SP1 Beta Build 7601,16562. Registrars have two options to download SP1, either via Windows Update or download the ISO, which contains both 32-bit and 64-bit versions of Windows 7 and Windows Server 2008 R2.
Register and download Windows 7 SP1 Beta and Windows Server 2008 R2 SP1 Beta on TechNet Evaluation Center.
To register, you must fill out a questionnaire, which has more to do with IT professionals. Users who want to skip the registration process to download SP1 Beta just can use the following direct download links to download the official SP1 Beta to server Microsoft.
Windows 7 SP1 Beta 32-bit (x86) edition (updated through Windows): WUSignUpTool_x86.exe
Windows 7 SP1 Beta 64-bit (x64) edition (updated through Windows): WUSignUpTool_x64.exe
Windows 7 SP1 Beta ISO: 7601.16562.100603-1800_Update_Sp_Wave0-B1SP1.0_DVD.iso
ISO has Windows6.1-KB976932-x86-INTL.exe (32-bit), Windows6.1-KB976932-x64-INTL (64-bit), and Windows6.1-KB976932-ia64-INTL.exe (IA-64 ), and runs on Windows 7 and Windows Server 2008 R2.
Note: The link to download the update for Windows 7 and Windows Server 2008 R2 SP1 Beta
Note that Windows 7 and Windows Server 2008 R2 SP1 Beta is available only in English, French, German, Japanese and Spanish. After installing the beta version, the system will expire on June 30, 2011, where by that time, users must upgrade to a newer or final assembly, or remove the SP1 beta.
Windows 7 and Windows Server 2008 R2 SP1 includes updates to bring personal computers and servers to the latest level of support ensures continuous improvement of Windows Operating System (OS), including previous system upgrade through Windows Update, as well as continued incremental updates to Windows 7 and Windows Server 2008 R2 platform, based on feedback from customers and partners, and is easy for organizations to deploy a single set of updates. For detailed changes and additional improvements in SP1, check the significant changes in Windows 7 SP1 and Windows Server 2008 R2 SP1 document, SP1 Beta FAQ and documentation for the SP1 Beta.
And, there is a guide to remove the Windows 7 or Windows Server 2008 R2 SP1 Beta is for people who want to remove and get rid of SP1.
Saturday, September 25, 2010
How to Uninstall completed and Disable Remote Desktop (Terminal Services) connections or sessions
From time to time, a user who is trying to establish a Terminal Services or Remote Desktop connection to Windows 7, Windows Vista, Windows Server 2008 (R2), Windows Server 2003, Windows Server 2000, Windows Home Server or other RDP-server supports could face " terminal server has exceeded the maximum number of allowed connections "error message.
The error occurs because there the previous sessions or existing RDP connection to the server or host that have not been disconnected or terminated correctly. To make matters worse, unless the terminal server on the network are fully connected to the remote clients, and no additional slots, it is possible for the administrator to sign the server using Terminal Services Manager, to kill any RDP connections.
Instead of rebooting or restarting the host or the server that the user wants to Remote Desktop or remote control, here's an alternative workaround to remotely disable or terminate "stuck" Terminal Services or Remote Desktop sessions and connections.
Method 1
Manager, Terminal Services or Remote Desktop Services Manager can be used to disable and reset any Terminal Services or Remote Desktop connections. Depending on your operating system, there are various ways to start and run the Terminal Services Manager.
Windows XP and Windows Server 2003 or earlier:
Click Start -> Run and type% SystemRoot% \ System32 \ tsadmin.exe
Windows Vista Windows Server 2008:
Click the Start button and type tsadmin.msc in the Start Search box.
Windows 7 and Windows Server 2008 R2 or later:
Click Start, type Remote Desktop Services Manager in the Start Search box.
Tip: The client operating system or workstation, server, remote administrator (RSAT) should be set for the Manager to exist.
After Remote Manager Desktop Services or Terminal Services Manager starts, right-click on the "Remote Desktop Services Manager" or "All options Servers" and select Connect to a computer.
Then type the name or IP-address of the server with remote desktop service that wants to be manageable.
Log on a remote server, if required.
Authenticated server will be listed on the left panel. Select the desired server is not responding to remote desktop session.
In the right pane, navigate to the Session.
Right-click on the session, which would be disabled and then click Disable.
Method 2
Run the command prompt window.
Authentication on the remote computer using the following "NET USE" command:
NET USE / user: Administrator \ \ server name or IP-address> \ C $
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For example, "NET USE / user: Administrator \ \ 188.8.8.8 \ C $.
Enter a password.
Terminate any existing Remote Desktop or Terminal Services connection with the following command:
Reset session / server: server name or IP-address
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For, enter the number gradually, starting with 1, 2, 3 ... until the message "N ID session not found" it had been returned as an error when running. For example, the "reset session 1 / server: 188.8.8.8".
Tip: Do not notified will be displayed when a session is successfully completed.
Method 3
Running a Command Prompt window, and to authenticate remote host using the following "NET USE" command:
NET USE / user: Administrator \ \ server name or IP-address> \ C $
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For example, "NET USE / user: Administrator \ \ 188.8.8.8 \ C $.
Enter a password.
In addition, from Windows Explorer, map a network drive share folder on the target server, and log, respectively.
At the command prompt, type the following command:
qwinsta / server: server name or IP-address
Where is the server name or IP-address is the actual computer name or IP-address of the remote host. For example, "qwinsta / server: 188.8.8.8".
The list of active connections and Remote Desktop or Terminal Services Session will be displayed. Define "hung" connections and its identifier.
To reset and disable the remote desktop or session, run the following command:
rwinsta / server: server name or IP-address
Replace with the session ID is identified with the "qwinsta" command, and server name or IP-address on the actual computer name or IP-address of the remote host. For example, "rwinsta 1 / server: 188.8.8.8"
Note: qwinsta a query window station and dumped rwinsta Window Station.
After the Remote Desktop or Terminal Services connection or conversation stops and the disabled, the slot will be released and the remote user can remotely login again.
The error occurs because there the previous sessions or existing RDP connection to the server or host that have not been disconnected or terminated correctly. To make matters worse, unless the terminal server on the network are fully connected to the remote clients, and no additional slots, it is possible for the administrator to sign the server using Terminal Services Manager, to kill any RDP connections.
Instead of rebooting or restarting the host or the server that the user wants to Remote Desktop or remote control, here's an alternative workaround to remotely disable or terminate "stuck" Terminal Services or Remote Desktop sessions and connections.
Method 1
Manager, Terminal Services or Remote Desktop Services Manager can be used to disable and reset any Terminal Services or Remote Desktop connections. Depending on your operating system, there are various ways to start and run the Terminal Services Manager.
Windows XP and Windows Server 2003 or earlier:
Click Start -> Run and type% SystemRoot% \ System32 \ tsadmin.exe
Windows Vista Windows Server 2008:
Click the Start button and type tsadmin.msc in the Start Search box.
Windows 7 and Windows Server 2008 R2 or later:
Click Start, type Remote Desktop Services Manager in the Start Search box.
Tip: The client operating system or workstation, server, remote administrator (RSAT) should be set for the Manager to exist.
After Remote Manager Desktop Services or Terminal Services Manager starts, right-click on the "Remote Desktop Services Manager" or "All options Servers" and select Connect to a computer.
Then type the name or IP-address of the server with remote desktop service that wants to be manageable.
Log on a remote server, if required.
Authenticated server will be listed on the left panel. Select the desired server is not responding to remote desktop session.
In the right pane, navigate to the Session.
Right-click on the session, which would be disabled and then click Disable.
Method 2
Run the command prompt window.
Authentication on the remote computer using the following "NET USE" command:
NET USE / user: Administrator \ \ server name or IP-address> \ C $
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For example, "NET USE / user: Administrator \ \ 188.8.8.8 \ C $.
Enter a password.
Terminate any existing Remote Desktop or Terminal Services connection with the following command:
Reset
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For
Tip: Do not notified will be displayed when a session is successfully completed.
Method 3
Running a Command Prompt window, and to authenticate remote host using the following "NET USE" command:
NET USE / user: Administrator \ \ server name or IP-address> \ C $
Replace the server name or IP-address with the actual NetBIOS name or IP-address of the remote host. For example, "NET USE / user: Administrator \ \ 188.8.8.8 \ C $.
Enter a password.
In addition, from Windows Explorer, map a network drive share folder on the target server, and log, respectively.
At the command prompt, type the following command:
qwinsta / server: server name or IP-address
Where is the server name or IP-address is the actual computer name or IP-address of the remote host. For example, "qwinsta / server: 188.8.8.8".
The list of active connections and Remote Desktop or Terminal Services Session will be displayed. Define "hung" connections and its identifier.
To reset and disable the remote desktop or session, run the following command:
rwinsta
Replace
Note: qwinsta a query window station and dumped rwinsta Window Station.
After the Remote Desktop or Terminal Services connection or conversation stops and the disabled, the slot will be released and the remote user can remotely login again.
How do I delete or remove KB971033 Windows 7 activation pack (cotton)
Microsoft has released an update for Windows 7 Activation Technologies (KB971033), which increases its effectiveness and success of the existence of more than 70 well-known and potentially dangerous activation bypasses, cracks or exploits.
For Windows 7, users who use fake or pirated copies of Windows 7 on a machine, KB971033 can potentially causing havoc in the computer system, including frequent and persistent nag message on the screen to remind users to come true.
For non-genuine or illegitimate copies of Windows 7 users, the best and recommended approach is to install the KB970133 update, which provides that WATU (WAT update). For users who have installed KB970133, here is a guide to remove and uninstall the service pack KB970133, KB970133, it is not a required upgrade. Procedure, just as all updates and patches can be removed.
Go to Control Panel -> Programs -> Programs and Features -> Uninstall a program.
Click on the View updates installed on the left panel.
Select and highlight Update for Microsoft Windows (KB971033).
Click on "Delete."
K971033 will be removed from the system.
The package can be removed via the command prompt with administrator privileges:
x86 (32-bit) systems:
DISM / Internet / remove packages / PackageName: Microsoft-Windows-Security-WindowsActivationTechnologies-Package ~ 31bf3856ad364e35 ~ x86 ^ 7.1.7600.16395
x64 (64-bit) systems:
DISM / Internet / remove packages / PackageName: Microsoft-Windows-Security-WindowsActivationTechnologies-Package ~ 31bf3856ad364e35 ~ amd64 ~ ~ 7.1.7600.16395
Note that even your system has been marked as not genuine, remove KB971033 WAT update will not make the system a true again. The best work around is not a true system in order to remove the crack or hack loader, which was the source marks the wool, and then do the upgrade (to lose the remaining rearm count, if all rearms allowed it was used or depleted). If you have a valid and legitimate product key, change the product key. Then run the test again force test to test the system again by running the following command at a command prompt with administrator privileges:
% SystemRoot% \ system32 \ Wat \ WatAdminSvc.exe / Run
Verification takes about 2-5 minutes, and you may need to log off or reboot for all nags disappear.
Other alternatives can be done system restore to a restore point before KB971033 was installed. Or just delete failed to crack or loader, and install new cracked or OEM BIOS Loader for Windows 7 that works, and then re-validate the system using the command above.
In any case, Windows 7 SP1 will include the KB971033 by default. By that time, KB971033 WAT upgrade is unlikely to be separable or impossible to establish. However, users can disable WATU files without deleting the following command (run from the command prompt with administrator privileges):
takeown / p "% WINDIR% \ System32 \ Wat \ *" & & ICACLS "% WINDIR% \ System32 \ Wat \ *" / deny * S-1-1-0: F
And, deleting scheduled tasks using the WAT run validation checks. WATU Shedualer Trust uses to test the system once you reboot when you first set and again every 90 days. To disable the related problems, run the following commands at the command prompt with administrator privileges:
schtasks / modify / disable / t "\ Microsoft \ Windows \ Windows Activation Technologies \ ValidationTask" & & schtasks / modify / disable / t "\ Microsoft \ Windows \ Windows Activation Technologies \ ValidationTaskDeadline"
For Windows 7, users who use fake or pirated copies of Windows 7 on a machine, KB971033 can potentially causing havoc in the computer system, including frequent and persistent nag message on the screen to remind users to come true.
For non-genuine or illegitimate copies of Windows 7 users, the best and recommended approach is to install the KB970133 update, which provides that WATU (WAT update). For users who have installed KB970133, here is a guide to remove and uninstall the service pack KB970133, KB970133, it is not a required upgrade. Procedure, just as all updates and patches can be removed.
Go to Control Panel -> Programs -> Programs and Features -> Uninstall a program.
Click on the View updates installed on the left panel.
Select and highlight Update for Microsoft Windows (KB971033).
Click on "Delete."
K971033 will be removed from the system.
The package can be removed via the command prompt with administrator privileges:
x86 (32-bit) systems:
DISM / Internet / remove packages / PackageName: Microsoft-Windows-Security-WindowsActivationTechnologies-Package ~ 31bf3856ad364e35 ~ x86 ^ 7.1.7600.16395
x64 (64-bit) systems:
DISM / Internet / remove packages / PackageName: Microsoft-Windows-Security-WindowsActivationTechnologies-Package ~ 31bf3856ad364e35 ~ amd64 ~ ~ 7.1.7600.16395
Note that even your system has been marked as not genuine, remove KB971033 WAT update will not make the system a true again. The best work around is not a true system in order to remove the crack or hack loader, which was the source marks the wool, and then do the upgrade (to lose the remaining rearm count, if all rearms allowed it was used or depleted). If you have a valid and legitimate product key, change the product key. Then run the test again force test to test the system again by running the following command at a command prompt with administrator privileges:
% SystemRoot% \ system32 \ Wat \ WatAdminSvc.exe / Run
Verification takes about 2-5 minutes, and you may need to log off or reboot for all nags disappear.
Other alternatives can be done system restore to a restore point before KB971033 was installed. Or just delete failed to crack or loader, and install new cracked or OEM BIOS Loader for Windows 7 that works, and then re-validate the system using the command above.
In any case, Windows 7 SP1 will include the KB971033 by default. By that time, KB971033 WAT upgrade is unlikely to be separable or impossible to establish. However, users can disable WATU files without deleting the following command (run from the command prompt with administrator privileges):
takeown / p "% WINDIR% \ System32 \ Wat \ *" & & ICACLS "% WINDIR% \ System32 \ Wat \ *" / deny * S-1-1-0: F
And, deleting scheduled tasks using the WAT run validation checks. WATU Shedualer Trust uses to test the system once you reboot when you first set and again every 90 days. To disable the related problems, run the following commands at the command prompt with administrator privileges:
schtasks / modify / disable / t "\ Microsoft \ Windows \ Windows Activation Technologies \ ValidationTask" & & schtasks / modify / disable / t "\ Microsoft \ Windows \ Windows Activation Technologies \ ValidationTaskDeadline"
Subscribe to:
Posts (Atom)