Showing posts with label Windows Server 2008. Show all posts
Showing posts with label Windows Server 2008. Show all posts

Sunday, May 6, 2012

bench3

Migration from Novell to 2008R2

How to migrating Windows XP workstations on Novel into a 2008R2 domain. Where, most workstations have only one primary user and profiles are stored locally. The My Documents folder is being redirected to a NetWare mapped drive. Can USMT migrate the local profile to a roaming profile stored on 2008R2?

Eventually the workstation will be migrated to 7. Do we hold off on roaming profiles until then? Can 7 go from local to roaming profile?

Go from local profile to local profile. Turn roaming on, afterwards. Simpler, cleaner, easier to troubleshoot. There will be those days.

Turning on roaming profiles once in a native Windows environment is simple, common and useful. However, check your network architecture to ensure you can handle this against what data is in those profiles. Large PST, Movies, etc will cause the user to think the new network or products (hint, hint) is not good.

Yes it can achieve this using UAMT 4 to migrate Windows XP local to 7 domain roaming.

Read More

Friday, February 17, 2012

bench3

Installing and Configuring FTP 7 On IIS 7 | Security and Deployment options Available On FTP 7.5

Microsoft rewrote the FTP service for Windows Server 2008 and above. This updated FTP service incorporates many new features that enable web authors to publish content better than before, and offers web administrators more security and deployment options.

The FTP 7.5 service ships as a feature for IIS 7.5 in Windows 7 and Windows Server 2008 R2.

The FTP 7.0 and FTP 7.5 services were shipped out-of-band for IIS 7.0, which required downloading and installing the service from the following URL: http://www.iis.net/download/FTP.

Some Of The Security and Deployment options Available On FTP 7.5

  • Integration with IIS: IIS has a new administration interface and configuration store, and the new FTP service is tightly integrated with this design. The old IIS 6.0 metabase is gone, and the updated configuration store based on the .NET XML-based *.config format took its place. In addition, IIS has an updated administration tool, and the new FTP server plugs seamlessly into that paradigm.
  • Support for new Internet standards: One of the most significant features in the updated FTP server is support for FTP over SSL. The FTP server also supports other Internet improvements such as UTF8 and IPv6.
  • Shared hosting improvements: By fully integrating into IIS, the updated FTP server makes it possible to host FTP and Web content from the same site by simply adding an FTP binding to an existing Web site. In addition, the FTP server has virtual host name support, making it possible to host multiple FTP sites on the same IP address. The FTP server also has improved user isolation, making it possible to isolate users through per-user virtual directories.
  • Custom authentication providers: The updated FTP server supports authentication using non-Windows accounts for IIS Managers and .NET Membership.
  • Improved logging support: FTP logging was enhanced to include all FTP-related traffic, unique tracking for FTP sessions, FTP sub-statuses, additional detail fields in FTP logs, and much more.
  • New supportability features: IIS has the option to display detailed error messages for local users, and the FTP server supports this by providing detailed error responses when logging on locally to an FTP server. The FTP server also logs detailed information using Event Tracing for Windows (ETW), which provides additional detailed information for troubleshooting.
  • Extensible feature set: FTP supports extensibility that allows you to extend the built-in functionality that ships with the FTP service. More specifically, there is support for creating your own authentication and authorization providers. You can also create providers for custom FTP logging and for determining the home directory information for your FTP users.
Read More

Friday, April 29, 2011

bench3

Use Windows Server 2008 Without Activation

In this post, we’ll know how to use Windows Server 2008 after the initial evaluation period that is 60 days without activation and entry of a product key.

Evaluating Windows Server 2008 software does not require product activation. Any edition of Windows Server 2008 may be installed without activation, and it may be evaluated for 60 days. Additionally, the 60-day evaluation period may be reset (re-armed) three times. This action extends the original 60-day evaluation period by up to 180 days for a total possible evaluation time of 240 days.

How to install Windows Server 2008 without activating it

  • During Windows Server 2008 Setup , when you are prompted to enter a product key for activation, do not enter a key. Click No when Setup asks you to confirm your selection.
  • You may be prompted to select the edition of Windows Server 2008 that you want to evaluate. Select the edition that you want to install.
  • When you are prompted, read the evaluation terms in the Microsoft Software License Terms, and then accept the terms.
  • When the Windows Server 2008 Setup program is finished, your initial 60-day evaluation period starts.

To check the time that is left on your current evaluation period, run the Slmgr.vbs script that is in the System32 folder. Use the -dli switch to run this script. The slmgr.vbs -dli command displays the number of days that are left in the current 60-day evaluation period.

How to manually extend the evaluation period
When the initial 60-day evaluation period nears its end, you can run the Slmgr.vbs script to reset the evaluation period. To do this, follow these steps:

  • Click Start, and then click Command Prompt.
  • Type slmgr.vbs -dli, and then press ENTER to check the current status of your evaluation period.
  • To reset the evaluation period, type slmgr.vbs –rearm, and then press ENTER.
  • Restart the computer

This resets the evaluation period to 60 days. Remember that you can do this three times.

Read More

Thursday, March 31, 2011

bench3

Windows Explorer Not Responding temporarily To File Share Requests When Copying File To A Share

Windows 7 having a problem when copying files to shares on our server (running Windows 2008 ). The file is copied but Explorer continues showing the dialog "Copying". The process cannot be killed with Task Manager and I am forced to restart manually the computer.

Consider the following scenario:

  • You have a computer that is running one of the following operating systems:
    • Windows Vista
    • Windows Server 2008
    • Windows 7
    • Windows Server 2008 R2
  • You share some files or some folders on the computer.
  • Some users try to access the shared files or the shared folders from remote computers.

In this scenario, the computer that shares the files and the folders may temporarily not respond to file share requests. When this issue occurs, users cannot enumerate the shared files or the shared folders on the computer.

Note The computer that shares the files and the folders resumes responding to requests for shared resources after 4 minutes.

Solution:

The only way to avoid this kind of problem is to try this hotfix:
KB2492806 - A Windows Vista-based, Windows Server 2008-based, Windows 7-based or Windows Server 2008 R2-based computer that shares some files and some folders may not respond to file share requests

Download Location: http://support.microsoft.com/kb/2492806

Also I found out that issuing the following commands at the Windows 7 machine solved the problem:

netsh interface tcp set global autotuninglevel=disabled
netsh int ip set global taskoffload=disabled

Read More

Wednesday, December 29, 2010

bench3

.Net 4.0 Is Not Included In Service Pack 1 Of Windows Server 2008 R2

Is net 4.0 part of service pack 1? Answer is probably no. It is not part of Windows Server 2008 R2 SP1, but we can install it with the Installer.

It is an important feature, and why it's not included in Windows Server 2008 R2 SP1:  
.net Framework will be inlcuced into Windows WHEN a tool inside the Windows needs it. It makes sense because not many many programs need .net 4.0 runtime and not many were written in net 4.0? So, it is adjustable as long as we can use the installer to make use of it when ever required.
Note: .Net 4.0 was Released To Manufacturing (RTM) in March 2010 after Windows 7 is out, so No Windows 7 tool uses it. But, the next version of Windows, Windows 8 will mostly include it. 
Related Post:
Fact: Currently the amount of tools which use .net 4.0 is very small. But it will grow. .Net 4.0 was released with Visual studio 2010 this year, so it takes a time until the first programs use it.
Read More

Monday, December 27, 2010

bench3

Windows 7 And Windows Server 2008 R2 Service Pack 1 | Improvements And New Features

Windows 7 Service Pack 1 is an update for consumers and IT Pros that helps keep your PCs supported, provides ongoing improvement to the operating system, includes previous updates delivered over Windows Update as well as continuing incremental updates to the Windows 7 platform based on customer and partner feedback, and is easy for organizations to deploy a single set of updates.
Windows Server 2008 R2 SP1 is an update for enterprises and IT Professionals that offers important virtualization enhancements to customers with the introduction of Dynamic Memory and Microsoft RemoteFX. It also includes previous improvements delivered via Windows Update and addresses feedback from customers. Windows Server 2008 R2 SP1 will have Dynamic Memory on Microsoft Hyper-V Server 2008 R2
Service Pack 1 will be released within the first half of calendar year 2011. However, Release Canditate Version SP1 is now available for download. The RC is best suited for IT Pros, tech enthusiasts, and developers who need to test the service pack in their organization or with the software they are developing. The final release of Service Pack 1 will be available through Windows Update for consumers when it is ready.
If you have already installed the RC Version of Windows 7, You cannot upgrade from the RC builds to the final build of SP1. You will have to uninstall the Service Pack or do a clean install of Windows 7 or Windows Server 2008 R2.
System Requirements For Service Pack 1:
Your current operating system must be the Release to Manufacturing (RTM) version of Windows 7 or Windows Server 2008 R2 (build 7600).
You cannot install the Release Candidate over the Beta of SP1. You must uninstall the beta. But you can install the RC on an evaluation version of Windows 7 or Windows Server 2008 R2.
There are several downloads available for Windows 7 And Windows Server 2008 R2 Service Pack 1. And if you are not sure of Which one you should choose, here is some simple tip for you. Actually, there are two ways you can obtain the service pack RC. You can download a special key to enable Windows Update to offer you the service pack RC, or you can download the service pack directly. For each download method, you should choose the correct download for your platform (x86, IA64 or x64).

Windows 7 is a high quality release and provides many benefits to consumers and businesses alike. SP1 will include all updates previously available to Windows 7 users through Windows Update, so there is no reason to wait or delay their use of Windows 7.

And there will not be a slipstream build of SP1 RC. The RC will only be available as the service pack update itself. You will need to have a release to manufacturing (RTM) version of Windows 7 or Windows Server 2008 R2 to install the RC of the service pack. And you will be able to uninstall the service pack RC if you need to.

Please note, it is always a best practice to back up your data prior to installing any RC software.
Warning! RC will stop functioning after a certain amount of time: You will be reminded beginning August 30, 2011. The RC will expire on November 30, 2011. You will have to upgrade to a newer build or uninstall and return to the RTM build by that time.
One of the major improvements included in Windows Server 2008 R2 SP1 is virtualization enhancements And for other improvements, please see the Notable Changes document for detail on the additional improvements in SP1.

Difference Between RemoteFX And  Remote Desktop Services.  How do they integrate:
RemoteFX describes a set of rich media capabilities that are available to customers using the Remote Desktop Services platform to deploy a virtual machine- or session-based remote desktop infrastructure. Specifically, RemoteFX enhances the Remote Desktop Protocol (RDP) in Remote Desktop Services so that remote workers can access any type of application or screen content, including rich media and 3D applications, improving end user productivity.
Read More