Microsoft windows services for unix — Ваш верный помощник с OS Windows

From Wikipedia, the free encyclopedia

Windows Services for UNIX

Other names	SFU, SUA
Original author(s)	MKS Inc. (SFU 1.0 / 2.0), Softway Systems, Inc. (SFU 3.0 / 3.5)
Developer(s)	Microsoft
Initial release	February 1999; 26 years ago
Final release	3.5 / January 2004; 21 years ago
Operating system	Microsoft Windows
Platform	IA-32 and x86-64
Predecessor	Microsoft POSIX subsystem
Successor	Windows Subsystem for Linux
Type	Compatibility layer
Website	Windows Services for Unix at the Wayback Machine (archived 2017-08-26)

Windows Services for UNIX (SFU) is a discontinued software package produced by Microsoft which provided a Unix environment on Windows NT and some of its immediate successor operating-systems.

SFU 1.0 and 2.0 used the MKS Toolkit; starting with SFU 3.0, SFU included the Interix subsystem,^[1] which was acquired by Microsoft in 1999 from US-based Softway Systems as part of an asset acquisition.^[2] SFU 3.5 was the last release and was available as a free download from Microsoft. Windows Server 2003 R2 included most of the former SFU components (on Disk 2), naming the Interix subsystem component Subsystem for UNIX-based Applications (SUA).^[3] In Windows Server 2008 and high-end versions of both Windows Vista and Windows 7 (Enterprise and Ultimate), a minimal Interix SUA was included, but most of the other SFU utilities had to be downloaded separately from Microsoft’s web site.^[1]

The Interix subsystem included in SFU 3.0 and 3.5 and later released as SUA Windows components provided header files and libraries that made it easier to recompile or port Unix applications for use on Windows; they did not make Linux or other Unix binaries (BSD, Solaris, Xenix etc) compatible with Windows binaries. Like the Microsoft POSIX subsystem that Interix replaced, it is best thought of as a distinct Unix-like platform.

It is replaced by Windows Subsystem for Linux in Windows 10 and Windows Server 2019.

KornShell running on SUA

C shell running on SUA

As of SFU 3.5, it contained:

Over 350 Unix utilities such as vi, ksh, csh, ls, cat, awk, grep, kill, etc.
GCC 3.3 compiler, includes and libraries (through an MS libc)
A cc-like wrapper for Microsoft Visual Studio command-line C/C++ compiler
GDB debugger
Perl
NFS server and client
A pcnfsd daemon
X11 tools and libraries
Tools for making NFS mount-points appear as Windows shares, and vice versa (gateway services)
A NIS server capability linked with Active Directory (AD)
Some Windows/Unix authentication information-synchronization tools

SFU did not contain the following:

bash, OpenSSH, sudo, CVS, ClamAV, bzip2, gmake, curl, emacs, Apache, XView, Ruby, Tcl, Python

Although SFU includes X Window System client libraries and applications, it does not contain a native X server. Administrators may configure any of the numerous third-party Windows X servers. Fully featured free options include Cygwin/X, Xming and WeirdX.

Microsoft produced at least one beta release of the initial version of SFU before its final release in February 1999. This release, in English only, was supported on the Windows NT 4.0 SP3+ for x86 and Alpha platforms. This is the only known release to support Alpha. It included a demonstration version of the MKS Toolkit along with the following components:

Telnet server
Telnet client
UNIX Utilities (from MKS)
Client for NFS
Server for NFS
Server for NFS Authentication
Windows NT to UNIX password-synchronization
Help files and documentation

This second installment of SFU was released April 2000 and was also for English; however, a Japanese-language release appeared just two months later in June 2000. Both ran on Windows NT 4.0 SP4+ and Windows 2000 on x86 platforms with Internet Explorer 4.01+. SFU 2.0 supported the following UNIX versions: Solaris 2.6+, HP-UX 10.2+, AIX 4.2+, Tru64 UNIX 5.0+, and Red Hat Linux 5.1+. It included the following components:

Server for NFS (NFSServer)
Client for NFS (NFSClient)
Gateway for NFS (NFSGateway)
Server for PCNFS (Pcnfsd)
User Name Mapping (Mapsvc)
Server for NFS Authentication (NFSServerAuth)
Server for NIS (NIS)
Telnet Client (TelnetClient)
Telnet server (TelnetServer)
Password synchronization (PasswdSync)
ActiveState ActivePerl (Perl)
UNIX utilities (UnixUtilities)
Cron service (CronSvc)
Rsh service (RshSvc)

There were subsequent updated OEM releases SFU 2.1, SFU 2.2, and SFU 2.3.

This version, released in May 2002, was the first release to include the Interix subsystem. Previously Microsoft had released Interix 2.2 (actually version 2.2.5) as a separate product around the same time frame as SFU 2.0. This SFU release included Interix release 3.0 (commonly called the «version» as reported by uname -r) with an internal Microsoft version of 7.0 that relates to internal build sequences. This Interix release contained significant technical extensions from the Interix 2.2 release such as a rooted file system and setuid functionality that were entirely based on the Softway Systems’ Interix development codenamed «Firebrand». This was also released in English and followed by a later release in Japanese in October 2002, adding internationalization support. Both supported Windows NT 4.0 SP6a+, Windows 2000, and Windows XP Professional on x86 platforms with Internet Explorer 5.0+. The MKS Toolkit was no longer included. It included the following components:

Base Utilities for Interix (BaseUtils; including X11R5 utilities)
UNIX Perl for Interix (UNIXPerl)
Interix SDK (InterixSDK; including headers and libraries for development and a wrapper for Visual Studio compiler)
GNU Utilities for Interix (GNUUtils, about 9 utilities in total)
GNU SDK for Interix (GNUSDK; including gcc and g++)
NFS Client for Windows (NFSClient)
NFS Gateway for Windows (NFSGateway)
NFS Server for Windows (NFSServer)
NIS Server for Windows (NIS)
Password Synchronization (PasswdSync)
Windows Remote Shell Service (RshSvc)
Telnet Server for Windows (TelnetServer)
NFS User Name Mapping (Mapsvc)
NFS Authentication Server (NFSServerAuth)
PCNFS Server (Pcnfsd)
ActiveState Perl (Perl)

This was the final release of SFU and the only release to be distributed free of charge. It was released January 2004 and included both English and Japanese versions for Windows 2000, Windows XP Professional, and Windows Server 2003 (original release only^[a]) on x86 platforms with Internet Explorer 5.0+. It included Interix subsystem release 3.5 (build version 8.0) adding internationalization support (at least for the English version which did not have such until now) and POSIX threading. This release could only be installed to an NTFS file system (earlier versions supported FAT; this was for improved file-security requirements in Interix 3.5). The following UNIX versions were supported for NFS components: Solaris 7 and 8, Red Hat Linux 8.0, AIX 5L 5.2, and HP-UX 11i. It included the following components:

Base Utilities for Interix (BaseUtils; including X11R6 and X11R5 utilities)
UNIX Perl for Interix (UNIXPerl)
Interix SDK (InterixSDK; including headers and libraries for development and a wrapper for Visual Studio compiler)
GNU Utilities for Interix (GNUUtils, again about 9 utilities)
GNU SDK for Interix (GNUSDK; including gcc and g++)
NFS Client for Windows (NFSClient)
NFS Gateway for Windows (NFSGateway)
NFS Server for Windows (NFSServer)
NIS Server for Windows (NIS)
Password synchronization (PasswdSync)
Windows Remote Shell Service (RshSvc)
Telnet Server for Windows (TelnetServer)
NFS User Name Mapping (Mapsvc)
NFS Authentication Server (NFSServerAuth)
PCNFS server (Pcnfsd)
ActiveState Perl (Perl)

Microsoft does not intend to produce any further standalone versions of SFU, opting instead for the integrated SUA. As of August 18, 2016, v3.5 is unavailable from the provided Microsoft Link.^[4] General support continued until 2011; extended support until 2014.^[5]

Character translation must be used to accommodate filenames which include a colon (:) or other characters that do not comply with the naming conventions of Windows file-systems. Files with the same name but different cases are also not allowed by default, but can be enabled on installation with the side-effect of making the underlying partition’s filesystem case-sensitive,^[6]^[7] even for the Win32 subsystem.

Network authentication for UNIX systems relies on the insecure NIS protocol (LDAP- and Kerberos-based authentication require a third-party solution). Microsoft has released several hotfixes for Windows Services for UNIX, and at least one Security Update (KB939778). The GNU Project utilities are several versions older than the latest ones. A separate port of the up-to-date Debian utilities was started in 2007, but apparently abandoned in 2009.^[8] Several of the text processing utilities in SUA (e.g. awk) are not compatible with Unicode or wide character text files.

No version of Windows Services for UNIX is available for Windows XP Professional x64 Edition.^[9]

Windows Server 2003 R2 contains most SFU components, namely Microsoft Services for Network File System (NFS), Subsystem for UNIX-based Applications (SUA, a.k.a. Interix), and Identity Management for UNIX.^[10] The July 2007 SFU 3.5 Security Update updated posix.exe and related files to match the SUA version.^[11]

Unlike the SFU, the SUA version included in Windows Server 2003 R2 (and subsequent versions) has 64-bit support and allows linking of Win32 libraries to SUA applications.^[12]

Windows Vista and Windows 7 Enterprise and Ultimate Editions also contain the Services for Unix components, now called the Subsystem for UNIX-based applications (SUA),^[3] and Client for NFS v3. Users must download the utilities and SDK separately. However, the server components from the SFU product line (namely Server for NFS, User Name Mapping, Server for NIS, Password Synchronization etc.) are not included^[13] – these are included in Server editions of Windows (i.e. Windows Server 2008).

SUA was deprecated in Windows 8 Enterprise^[14] and Windows Server 2012,^[15] and completely removed in Windows 8.1 and Windows Server 2012 R2.^[16] The NFS server is still supported in Windows Server 2012 R2.^[17]^[18]

The NFS client feature and server features are separate from the SUA in Windows 7 and 2008,^[19] and remained supported until Windows Subsystem for Linux replaced it. On desktop (Windows 7), NFS is only available in the Enterprise and Ultimate editions.^[20] The free reference implementation of NFS 4.1 for Windows (by UMICH CITI), the development of which was sponsored by Microsoft,^[21] does work on lower-end versions of Windows 7, but requires more involved installation.^[22]

In Windows 8, the NFS client gained krb5p (Kerberos 5 with full data encryption) support. In Windows 7, Kerberos 5 was supported for authentication, but only packet integrity checking was available for data. The maximum block/buffer size was also increased from 32 KB to 1 MB in Windows 8.^[23]

Windows Server 2012 added support for NFS 4.1 server.^[24]^[25] The new implementation is kernel-based (RPC/XDR-wise) but many optional features from NFS4 are not implemented, including ACLs, pNFS etc. There is however support in PowerShell for mapping user identities.^[26]

Cygwin
UnxUtils
UWIN
Windows Subsystem for Linux

^ Only works on «R1», not on R2

^ ^a ^b Dale Liu; Justin Peltier (2008). Next Generation SSH2 Implementation: Securing Data in Motion. Syngress. pp. 181–182. ISBN 978-1-59749-283-6. Archived from the original on September 30, 2014. Retrieved October 26, 2016.
^ «Microsoft Acquires Softway Systems to Strengthen Future Customer Interoperability Solutions» (Press release). Microsoft. September 17, 1999. Archived from the original on February 22, 2011. Retrieved December 28, 2010.
^ ^a ^b «Subsystem for UNIX-based Applications Overview». Microsoft. November 17, 2009. Retrieved August 20, 2022.
^ «Download details: Windows Services for UNIX Version 3.5». Microsoft. September 21, 2006. Archived from the original on April 14, 2006.
^ Mary Jo Foley (September 1, 2005). «It’s the End of the Line for Microsoft’s Services for Unix Product». eWeek Microsoft Watch. Archived from the original on September 5, 2012.
^ Charlie Russel (December 5, 2007). «Windows Services for UNIX 3.5 White Paper». Microsoft.
^ «Chapter 1: Introduction to Windows Services for UNIX 3.5». UNIX Custom Application Migration Guide, Volume 2: Migrate Using UNIX Services for Windows 3.5. Microsoft. December 5, 2007.
^ «Debian Interix Port». Debian-interix.net. Archived from the original on January 2, 2014. Retrieved January 10, 2014.
^ «You receive a «Cannot install on a 64 bit machine» error message when you try to install Windows Services for UNIX on a computer that is running a 64-bit operating system». Archived from the original on November 28, 2011. Retrieved August 11, 2011.
^ «Microsoft Windows Server 2003 R2 UNIX Interoperability Components». Microsoft. Archived from the original on May 10, 2005.
^ «Microsoft Security Bulletin MS07-053 — Important : Vulnerability in Windows Services for UNIX Could Allow Elevation of Privilege (939778)». Microsoft. Archived from the original on May 4, 2011. Retrieved March 8, 2011.
^ «Open Source at Microsoft. Subsystem for UNIX-Based Applications: Providing More Choices» (PDF). Archived (PDF) from the original on February 26, 2012. Retrieved May 30, 2011.
^ Ashish (May 1, 2007). «UNIX Interoperability and Windows Vista». Services for UNIX — Interoperability Blog, MSDN Blogs. Archived from the original on March 8, 2010.
^ Reiter, Brian (September 15, 2011). «SUA Deprecated in Windows 8». Archived from the original on June 9, 2012. Retrieved October 15, 2011. SUA is deprecated starting with [the Windows 8 M3 Developer Preview] release and will be completely removed from the next release.
^ «Features Removed or Deprecated in Windows Server 2012». August 31, 2016. Retrieved August 20, 2022.
^ «Features Removed or Deprecated in Windows Server 2012 R2 Preview». August 31, 2016. Retrieved August 20, 2022.
^ «Network File System Overview». Microsoft. August 31, 2016. Retrieved August 20, 2022.
^ Minasi, Mark; Greene, Kevin; Booth, Christian; Butler, Robert; McCabe, John; Panek, Robert; Rice, Michael; Roth, Stefan (2013). Mastering Windows Server 2012 R2. John Wiley & Sons. pp. 565 and 636. ISBN 978-1-118-33394-5.
^ «Installation & Configuration of Windows NFS Client to enable Windows to Mount a UNIX File System». Running SAP Applications on SQL Server blog. February 3, 2011. Retrieved August 20, 2022.
^ «Mount NFS Share Windows 7 | Zwiegnet Blog 2013 | Server Hosting». Blog.zwiegnet.com. Archived from the original on January 10, 2014. Retrieved January 10, 2014.
^ «Microsoft finances open-source NFS v4 implementation for Windows». ZDNet. Retrieved August 20, 2022.
^ «NFS Client in Windows 7 Pro». drink the sweet feeling of the colour zero. April 29, 2012. Retrieved August 20, 2022.
^ «Client for NFS in Windows 8». Services for UNIX — Interoperability blog. Archived from the original on January 10, 2014. Retrieved January 10, 2014.
^ «Server for NFS in Windows Server 2012». The Storage Team at Microsoft — File Cabinet Blog. September 14, 2012. Retrieved August 20, 2022.
^ «Microsoft storage boffins serve up smoking 2012 NFS server • the Register». The Register. Archived from the original on June 17, 2018. Retrieved September 18, 2017.
^ «NFSv4.1 Architecture and Tradeoffs in Windows Server 2012» (PDF). Archived (PDF) from the original on March 16, 2019. Retrieved August 9, 2018.

Microsoft TechNet: Windows Services for UNIX
Services for UNIX: Blog
Download: Windows Services for UNIX 3.5 at the Wayback Machine (archived January 13, 2016)
Download: Utilities and SDK for Subsystem for UNIX-based Applications in Microsoft Windows 7 and Windows Server 2008 R2 at the Wayback Machine (archived March 23, 2014)

Источник

Home > Windows > Review: Windows Services for UNIX

Everyone knows what Microsoft does by now. What some people do not know is that Microsoft releases a system integration software named Windows services for UNIX. The purpose of SFU is so that people who must administer UNIX server with a Microsoft Windows PC can do it with ease, it also serves as an application migration platform as well as way to run legacy UNIX applications from within a Windows environment.

SFU is a UNIX subsystem that is not emulation, it will allow you to run some legacy UNIX apps with native speeds and performance. What SFU is not, SFU is not a Linux distribution. SFU is not a UNIX variant. I recently got a chance to test Windows Services for UNIX 3.0. And I have to say I was mildly suprised with it.

System Requirements

SFU needs Windows 2000 Professional, Windows XP Professional or Windows NT 4.0 with Service Pack 6. It will not run on Windows 9x or Windows ME. You will also need at least 128 mb of RAM and 182 mb of Hard Disk space in order to have a full installation.

Installation

SFU installs like a common Windows application. Nothing special about it. The one thing I found counterintuitive, is that you have to agree to three different licenses at 3 different times throughout the installation, so if you install it you have to stay with your machine you cannot do an automated install.

Features

SFU is a very full featured application. You have a native Windows application installed that allows you to administer and create NFS shares. It comes with ActiveState Perl and a wide range of tools. It comes with the standard UNIX shells CSH and KSH, CRON and much more. The networking tools included with SFU were very good and I was able to do a lot with the other machines on my home network. Microsoft says that SFU will only support HP-UX, Solaris 8 and Red Hat Linux 7.0. I was able to administer SuSE Linux 8.1, along with Solaris 9 x86 and Red Hat Linux 9 along with FreeBSD. I was also able to do a remote installation of FreeBSD with SFU. You can access Mac OS X shares with the NFS tools.

The networking tools included are telnet, PING, Traceroute, netstat, SSH. With crontab you can set up times for any kind of maintence runs for the entire system not just the Interix subsystem. Scripting is also a strong point with SFU. You can run many UNIX scripts with very few modifications on the system. Perl Scripts can be run with ActiveState Perl. They also include Python with the system, but there is a native Windows port of Python available from the Python web site. The way that the Interix subsystem is set up reminds me of a UnixWare/Xenix setup, in terms of directory structure and the way things are setup The directory structure while running SFU is totally UNIX, all of the directories, /, /usr,/bin,/usr/bin,/lib,/dev all of them are under the SFU directory structure. For a wealth of UNIX command line tools SFU has them all and then some more.

The development environment consists of GNU Tools. GNUMake, GCC 2.0.7, and GDB. The development environment is extremely outdated so compiling and updating system libs and Applications was hard, I was able to compile bash as well
as lynx and some other text based applications but I was unable to compile recent graphics apps. KDE 3.1.2 was not going to happen, neither was GNOME 2. I called Microsoft support to find out if there was some place I could get updated packages and I was told that SFU was a migration tool only, its sole purpose is to make it easy for UNIX admins who wanted to come to Microsft Windows to help them port their Applications and services from UNIX to Windows as well as run some legacy UNIX apps and that SFU was in no way meant to be used as an Operating Environment. So no
help was on its way from Microsoft.

A while back when I used Interix, I was able to compile XFree86 and KDE 2 and GNOME 1.4 those services are no longer feasible in 3.0. While Interix 2 relied on many Cygnus functions you could just compile your source for Cygwin and use it on Interix. Microsoft has refined those functions and have taken out all of the Cygnus functionality so now a total port of the application is the only way anything will work.

Other system Integration tools that are much better are available. The prime candidate is Cygwin. Cygwin is available from Red Hat software. You have two versions of Cygwin that you can get. GNU Pro or it can be had for free, download from Red Hats website . If you are looking for a tool to help you work in a UNIX environment that is up to
date and has many of the creature comforts of Linux or UNIX, or if you are a Linux or UNIX hacker that must work with Windows and you want a familiar interface with which to work than Cygwin is the way to go. There are native ports of KDE 3.1.2 and GNOME 2 for Cygwin and all the major tools are available.

AT&T marketed a product a few years ago called UWIN, But that is also very out of date and is no longer enhanced.

Conclusion

While SFU has some good qualities about it I cannot justify the $99.00 price tag. If you are migrating to MS Windows then yes SFU is a good buy and is very helpful. If you are not migrating and just want to run UNIX /Linux tools and Applications then get Cygwin and save your cash.

Performance 10/10
Features 5/10
Affordability 6/10

Total 7/10

Источник

Introduction

Microsoft Windows Services for UNIX is a suite of network services designed to help enterprise customers integrate Windows into their existing UNIX-based environments. This innovative solution enables seamless communication and data exchange between Windows and UNIX systems, facilitating a more efficient and streamlined IT infrastructure. In this article, we will delve into the world of Microsoft Windows Services for UNIX, exploring its key features, system requirements, and installation process.

What is Microsoft Windows Services for UNIX?

Microsoft Windows Services for UNIX is a collection of network services that provide a bridge between Windows and UNIX systems. It allows users to access and manage UNIX-based systems from within the Windows environment, eliminating the need for separate UNIX workstations. This suite of services includes:

Services for NFS (Network File System): Enables users to access and manage NFS shares from within Windows.
Services for NIS (Network Information Service): Allows users to access and manage NIS databases from within Windows.
Services for SAMBA: Enables users to access and manage SAMBA shares from within Windows.
Services for SSH (Secure Shell): Provides secure remote access to UNIX-based systems from within Windows.

System Requirements

Microsoft Windows Services for UNIX requires supported operating systems, including:

Windows 2000: Service Pack 3 or later
Windows 2000 Service Pack 4: The latest service pack
Windows Server 2003: The latest service pack
Windows XP: Service Pack 1 or later

Installation Process

The installation process for Microsoft Windows Services for UNIX involves the following steps:

Download the installation package: Obtain the installation package from the Microsoft website.
Run the installation program: Execute the installation program and follow the on-screen instructions.
Select the components to install: Choose the components to install, such as Services for NFS, Services for NIS, and Services for SSH.
Configure the services: Configure the services according to your system requirements.
Test the services: Test the services to ensure they are functioning correctly.

Benefits of Microsoft Windows Services for UNIX

Microsoft Windows Services for UNIX offers several benefits, including:

Seamless integration: Enables seamless communication and data exchange between Windows and UNIX systems.
Improved productivity: Allows users to access and manage UNIX-based systems from within the Windows environment, eliminating the need for separate UNIX workstations.
Enhanced security: Provides secure remote access to UNIX-based systems from within Windows.
Simplified management: Enables administrators to manage UNIX-based systems from within the Windows environment.

Troubleshooting Microsoft Windows Services for UNIX

Common issues with Microsoft Windows Services for UNIX include:

Installation errors: Errors during the installation process can prevent the services from functioning correctly.
Configuration issues: Incorrect configuration of the services can prevent them from functioning correctly.
Security issues: Security vulnerabilities in the services can compromise the security of the system.

Conclusion

Microsoft Windows Services for UNIX is a powerful tool for integrating Windows into existing UNIX-based environments. Its suite of network services provides seamless communication and data exchange between Windows and UNIX systems, facilitating a more efficient and streamlined IT infrastructure. By understanding the system requirements, installation process, and benefits of Microsoft Windows Services for UNIX, administrators can ensure a smooth and successful implementation.

System Requirements for Microsoft Windows Services for UNIX

Operating System	Service Pack	Disk Space Required
Windows 2000	Service Pack 3 or later	100 MB
Windows 2000 Service Pack 4	The latest service pack	100 MB
Windows Server 2003	The latest service pack	100 MB
Windows XP	Service Pack 1 or later	100 MB

Installation Steps for Microsoft Windows Services for UNIX

Download the installation package: Obtain the installation package from the Microsoft website.
Run the installation program: Execute the installation program and follow the on-screen instructions.
Select the components to install: Choose the components to install, such as Services for NFS, Services for NIS, and Services for SSH.
Configure the services: Configure the services according to your system requirements.
Test the services: Test the services to ensure they are functioning correctly.

Troubleshooting Microsoft Windows Services for UNIX

Common issues with Microsoft Windows Services for UNIX include:

Installation errors: Errors during the installation process can prevent the services from functioning correctly.
Configuration issues: Incorrect configuration of the services can prevent them from functioning correctly.
Security issues: Security vulnerabilities in the services can compromise the security of the system.

Microsoft Windows Services for UNIX: Frequently Asked Questions

Q: What is Microsoft Windows Services for UNIX?
A: Microsoft Windows Services for UNIX is a suite of network services designed to help enterprise customers integrate Windows into their existing UNIX-based environments.

Q: What are the system requirements for Microsoft Windows Services for UNIX?
A: The system requirements for Microsoft Windows Services for UNIX include Windows 2000, Windows 2000 Service Pack 3 or later, Windows 2000 Service Pack 4, Windows Server 2003, and Windows XP.

Q: How do I install Microsoft Windows Services for UNIX?
A: To install Microsoft Windows Services for UNIX, download the installation package from the Microsoft website, run the installation program, select the components to install, configure the services, and test the services.

Q: What is Microsoft Windows Services for UNIX?

A: Microsoft Windows Services for UNIX is a suite of network services designed to help enterprise customers integrate Windows into their existing UNIX-based environments. It allows users to access and manage UNIX-based systems from within the Windows environment, eliminating the need for separate UNIX workstations.

Q: What are the system requirements for Microsoft Windows Services for UNIX?

A: The system requirements for Microsoft Windows Services for UNIX include:

Windows 2000: Service Pack 3 or later
Windows 2000 Service Pack 4: The latest service pack
Windows Server 2003: The latest service pack
Windows XP: Service Pack 1 or later

Q: How do I install Microsoft Windows Services for UNIX?

A: To install Microsoft Windows Services for UNIX, follow these steps:

Download the installation package: Obtain the installation package from the Microsoft website.
Run the installation program: Execute the installation program and follow the on-screen instructions.
Select the components to install: Choose the components to install, such as Services for NFS, Services for NIS, and Services for SSH.
Configure the services: Configure the services according to your system requirements.
Test the services: Test the services to ensure they are functioning correctly.

Q: What are the benefits of Microsoft Windows Services for UNIX?

A: The benefits of Microsoft Windows Services for UNIX include:

Seamless integration: Enables seamless communication and data exchange between Windows and UNIX systems.
Improved productivity: Allows users to access and manage UNIX-based systems from within the Windows environment, eliminating the need for separate UNIX workstations.
Enhanced security: Provides secure remote access to UNIX-based systems from within Windows.
Simplified management: Enables administrators to manage UNIX-based systems from within the Windows environment.

Q: Can I use Microsoft Windows Services for UNIX with other operating systems?

A: Yes, Microsoft Windows Services for UNIX can be used with other operating systems, including Windows 2000, Windows 2000 Service Pack 3 or later, Windows 2000 Service Pack 4, Windows Server 2003, and Windows XP.

Q: How do I troubleshoot Microsoft Windows Services for UNIX?

A: Common issues with Microsoft Windows Services for UNIX include:

Installation errors: Errors during the installation process can prevent the services from functioning correctly.
Configuration issues: Incorrect configuration of the services can prevent them from functioning correctly.
Security issues: Security vulnerabilities in the services can compromise the security of the system.

Q: Can I use Microsoft Windows Services for UNIX with a firewall?

A: Yes, Microsoft Windows Services for UNIX can be used with a firewall. However, you may need to configure the firewall to allow incoming and outgoing traffic on the required ports.

Q: How do I configure Microsoft Windows Services for UNIX?

A: To configure Microsoft Windows Services for UNIX, follow these steps:

Launch the Services for UNIX console: Launch the Services for UNIX console and select the services you want to configure.
Configure the services: Configure the services according to your system requirements.
Test the services: Test the services to ensure they are functioning correctly.

Q: Can I use Microsoft Windows Services for UNIX with a virtual private network (VPN)?

A: Yes, Microsoft Windows Services for UNIX can be used with a VPN. However, you may need to configure the VPN to allow incoming and outgoing traffic on the required ports.

Q: How do I uninstall Microsoft Windows Services for UNIX?

A: To uninstall Microsoft Windows Services for UNIX, follow these steps:

Launch the Add or Remove Programs console: Launch the Add or Remove Programs console and select Microsoft Windows Services for UNIX.
Click Remove: Click Remove to uninstall the services.
Follow the on-screen instructions: Follow the on-screen instructions to complete the uninstallation process.

Q: Can I use Microsoft Windows Services for UNIX with a third-party software?

A: Yes, Microsoft Windows Services for UNIX can be used with a third-party software. However, you may need to configure the software to work with the services.

Q: How do I contact Microsoft support for Microsoft Windows Services for UNIX?

A: To contact Microsoft support for Microsoft Windows Services for UNIX, visit the Microsoft website and select the support option. You can also contact Microsoft support directly by phone or email.

Источник

Материал из РУВИКИ — свободной энциклопедии

Подсистема для приложений на базе UNIX (англ. Subsystem for UNIX-based Applications, SUA), также известная как Сервисы Microsoft Windows для UNIX (англ. Microsoft Windows Services for UNIX, SFU) — программный пакет, разработанный компанией Microsoft, обеспечивающий подсистему UNIX и другие части среды UNIX на системах семейства Windows NT и более поздних. Расширена из ограниченной подсистемы POSIX Windows NT, и в дальнейшем заменила её.

Начиная с версии 3.0 (Windows XP, 1999 год) использует подсистему Interix^[1], которая была получена компанией Microsoft в 1999 году как часть имущества Softway Systems^[2]. В Windows Server 2003 R2 было переименовано в Подсистему для приложений на базе UNIX.

Подобно подсистеме POSIX в Windows NT, Interix не эмулирует ядро UNIX, а реализует подсистему пользовательского режима, работающую напрямую на ядре Windows NT.

Как и подсистема Microsoft POSIX в Windows NT, Interix не эмулирует работу ядра Unix,
это лишь реализация на уровне пользователя, запущенная поверх ядра Windows NT.

Важно, что и Cygwin (свободная альтернатива Interix), и Windows Services for Unix предлагают заголовочные файлы и библиотеки, что упрощает перекомпиляцию приложений Unix для их использования в Windows. Естественно, форматы исполняемых файлов Windows и Unix по-прежнему остаются несовместимыми.

Текущая версия включает:

Более 350 утилит Unix, таких, как vi, ksh, csh, ls, cat, awk, grep, kill, и т. п.
компилятор GCC 3.3, в том числе заголовочные файлы и библиотеки (через Microsoft libc)
cc-подобный упаковщик для C/C++ компилятора командной строки Microsoft Visual Studio
отладчик GDB
сервер и клиент NFS
Демоны pcnfsd
Утилиты и библиотеки X11
Утилиты для монтирования ресурсов NFS, таких, как разделяемые каталоги Windows, и наоборот (гейтвеи)
Сервер Network Information Service, сопряжённый с Active Directory
Некоторые утилиты синхронизации токенов аутентификации Windows и Unix

SFU не включает в себя (однако, их возможно установить отдельно):

bash, OpenSSH, sudo, CVS, ClamAV, bzip2, gmake, curl, emacs, Apache, XView, Ruby, Tcl, Python.

SFU не содержит встроенного X-сервера (только утилиты и библиотеки, как упоминалось выше), но может быть использован практически любой из имеющихся, например, Cygwin/X, Xming, WeirdMind или WeirdX.

Последний релиз — 3.5 от ноября 2007 года.

Windows Server 2003 R2 содержит довольно много предустановленных компонентов SFU, в том числе сервисы Microsoft для сетевой файловой системы (NFS), подсистема для приложений UNIX (Interix) и управление аутентификацией для UNIX.

Windows Vista Enterprise и Ultimate Editions также содержат элементы SFU, переименованную в подсистему для приложений UNIX (англ. Subsystem for UNIX-based applications, SUA).

Microsoft не планирует далее выпускать отдельные версии данного пакета. Возможность скачать последнюю версию с официального сайта будет доступна, по крайней мере, до 2009 года, официальная общая поддержка оканчивается в 2011, расширенная поддержка — в 2014.

Microsoft Windows Services for UNIX предназначен для Windows редакций Server и Professional. Потребительскими версиями Windows не поддерживается.

Windows 7 Enterprise/Ultimate Edition родная (native) поддержка (пакет встроен в систему)
Windows Server 2003
Windows XP Professional с Service Pack 1 или более поздним
Windows 2000 Server или Professional с Service Pack 3 или более поздним

Cygwin
MKS Toolkit
OpenNT
UnxUtils^[en], набор утилит и портов GNU UNIX в Win32.
Windows Subsystem for Linux — функциональный аналог в Windows 10 с лета 2016 года

↑ Dale Liu; Justin Peltier. Next Generation SSH2 Implementation: Securing Data in Motion (англ.). — Syngress, 2008. — P. 181—182. — ISBN 9781597492836.
↑ Microsoft Acquires Softway Systems to Strengthen Future Customer Interoperability Solutions, Sep 17, 1999, Press Release, Microsoft Corporation. Дата обращения: 30 августа 2011. Архивировано 22 февраля 2011 года.

Microsoft TechNet: Сервисы Windows для UNIX (англ.)
История подсистемы Interix (англ.), в PDF (то же в) (англ.)
Дополнительные свободные бинарные сборки для Interix (англ.)
Скрипт для конвертации атрибутов файлов UNIX в SFU (англ.)

Источник

In a heterogeneous network environment with Windows and Unix (or Linux) machines, there can often arise a need for cross platform data/service access. For instance, if a Windows client wants to access a Unix server, then a package like Samba can be set up on the Unix server. A similar need may arise for giving Unix users access to Windows
machines. This is where Windows Services for Unix (SFU) comes in, which acts as a gateway between Unix and Windows machines. It works on Windows–NT Server and Workstation, 2000 Pro and Server, and XP Pro. We installed it on Win 2000 Server Domain Controller and Win XP Pro machines. The installation was easy with minimal prompts.

Once installed, the product can be configured through an MMC (Microsoft Management Console). The right pane of the console, where the configuration parameters are keyed in, has a Web-based look. This is a good move to provide Unix administrators, who haven’t worked with MMC, a familiar interface. The Unix machine we used was running PCQLinux 7.1 (based on RedHat 7.1).

All the components of Windows Services for Unix 3.0 can be configured though a intuitive Web-based interface

Snapshot

MICROSOFT WINDOWS SERVICES FOR UNIX 3.0

Price:

Rs 4,350 (via special order). Also requires Win 2000 Client access licenses

Meant
for:

Networks running Windows and Unix environments

Feature:

Servers for NFS, PCNFS, NIS and telnet, Windows clients for NFS and Telnet; user mapping and password synchronization between Windows and Unix; Unix shell environment (Interix), compilers/interpreters and libraries, Web-based interface for administration

Pros:

Easy to install and set up (for basic requirements); easy to use configuration with Web look-n-feel; right click file sharing with Unixes; powerful Unix shell environment; comprehensive and detailed help, extensive logging

Cons:

Only NTLM authentication supported for secure Telnet, NFS shares accessible even when user account is disabled, old C and X11 libraries

Contact:

Tech Pacific India, Delhi.

Tel:

011-6325113

E-mail:

snehal@techpacindia

There’s a “Server for NFS” component that has to be set up for sharing directories with Unix clients. Once set up, sharing directories is as easy as creating a Windows share, and it also creates a similar hand icon on the folder. This, however, appears only when you refresh the explorer’s view. Moreover, if this NFS shared folder is also made into a Windows share, then the latter’s graphical representation takes over. So you have no means of knowing that this folder is also an NFS share. There’s also a client for NFS component that can be installed on all Windows machines wanting to access shared directories in Unix. If you don’t want the hassle of installing an NFS client on each Windows machine, there’s a Gateway for NFS component. This allows Windows machines to access NFS shares. A User Name Mapping (UNM) service controls access to the NFS shares. It allows Windows users and groups to be mapped to the same on Unix. The system administrator should be extra careful in not mapping an unprivileged Unix user to a privileged Windows user (say the administrator). UNM does display a warning when you attempt to map a Unix user to Windows administrator. There is simple as well as advanced mapping. In simple mapping, SFU automatically maps similar named users and groups across Windows and Unix. With advanced mapping, one can map them manually. UNM can pick up Unix users and groups info from the password files or negotiates with an NIS (Network Information Service) for the same. We tested the UNM with an NIS service running on PCQLinux. Given only the NIS domain name, UNM could pick up the exported information by the
NIS.

We found one small glitch in the mapping. Suppose a user account is created on the Windows server and mapped to a Unix/Linux user. This account is then given full access to an NFS share from Windows as well as Unix. Now, if the Windows counterpart of the mapped account is disabled, the NFS share is still accessible from the Unix machine. It’s only when the user’s account is deleted that the privileges are removed.

The “Server for NIS” component we just mentioned uses the Active Directory to store the NIS data, therefore must be installed on a domain controller. There’s a migration wizard to migrate NIS data to Active Directory. Since PCQLinux creates a group name same as a user name (by default) conflicts occurred during the migration of the group map after the passwd map. But the causes of the conflicts were obvious and clearly stated in the log file.

There’s a Telnet server that only supports NTLM authentication for secure access. Therefore, we were able to connect to the Telnet server only using plaintext authentication, since Linux does not support the former authentication. The need for a secure remote shell like SSH (Secure Shell) remains unquenched. Telnet server cannot be installed on a Windows XP machine.

With the password synchronization component, same passwords can be maintained across the mapped Windows and Unix users. That is, a user (say shekhar) will have the same password to log into the Windows machine as well as Unix machine.

This is the only component for which we had to jump out of the SFU graphical configuration and set up things on the Linux machine. For the synchronization to work, an SSOD (Single Sign-On Daemon) should be running on the Unix machine.

SSOD was available on the SFU CD for HP-UX version 11, IBM AIX version 4.3.3, RedHat Linux 7.0 and Solaris 7 on Sparc. We were able to set up SSOD easily on PCQLinux 7.1 and achieve Windows to Unix password synchronization. That is, if the password of a user is changed on Windows, it also changes on Linux. SSOD can also be set up to work with NIS where it will execute the NIS Makefile on a password change. For Unix to Windows password sync to work, a PAM (Pluggable Authentication Module) had to be set up. The PAM module required for the same is available for the above mentioned Unixes. But the only way to stop the running SSOD daemon, is to force kill it (ps —9
).

The component of SFU worth applause is Interix. It’s a full-fledged Unix shell environment running within Windows. The Interix subsystem provides Korn and C shell environments with all the popular Linux shell commands and utilities. It also includes libraries–C, C++, Perl, Fortran, tcl/tk–GNU compilers (gcc,g++) and interpreters (ActiveState Perl). We were able to successfully run some Linux shell scripts and command line Perl programs. For task scheduling, Interix provides the popular cron daemon, which installs as a Windows service and executes the tasks specified in a crontab file picked up from Linux. The X11R5 (release 5), libc (version 3) and NCURSES libraries are provided. The X11 and libc libraries are of old versions though, with the latest versions being libc 6 (also called glibc) and X11R6.6 (release 6.6).

The Bottom Line: SFU 3.0 is a useful service if you want to narrow down Windows and Unix administration. But to work with it, the administrator must be conversant with both Windows and Unix concepts.

Shekhar Govindarajan at PCQ Labs

Stay connected with us through our social media channels for the latest updates and news!

Источник