Consider the following scenario:

• On a Windows Server 2008-based or Windows Vista Service Pack 1 (SP1)-based computer, an application writes to a file on a local file share.
• This file is scanned by using memory-mapped files. This scanning process typically occurs when certain antivirus software is installed on the computer.

In this scenario, additional character spaces may be added to sections of the file. Therefore, the file becomes corrupted.

On a Windows Vista-based computer or on a Windows Server 2008-based client computer, you create a shortcut to a DFS link in the Favorite Links folder (%Userprofile%\Links). However, when you try to click the shortcut in Windows Explorer, the contents of the DFS share do not appear.

Note: This problem does not occur if the shortcut points to a DFS root folder or if the shortcut uses the UNC path for the target share.

Consider the following scenario:

• You work with a Windows Vista-based computer that is a member of a workgroup.
• On this computer, you try to access an administrative share that is located on another Windows Vista-based computer.
• The computer that you try to access is a member of a workgroup or a member of a domain. For example, you try to access the C$ administrative share.
• When you are prompted for your user credentials, you provide the user credentials of an administrative user account on the destination computer.

In this scenario, you receive the following error message:
Logon unsuccessful:

Windows is unable to log you on.
Make sure that your user name and password are correct.

If you try to map a network drive to the administrative share by using the Net Use command, you receive the following error message after you enter the correct credentials:

System error 5
has occurred. Access is denied.

When you redirect the Documents folder on a Windows Vista-based computer to a network share, the folder name unexpectedly changes back to Documents. You expect the folder name to be the user name.

This behavior may create many Documents folders on the network share. If you try to rename one Documents folder, all the other Documents folders change to that name.

Accessing shares or mapping drives using IPv6 addresses will fail.

Examples of failing commands:

net use * \\2001:db8:0:1::9\c$ ()

Or try to access the address through Start->Run.

\\2001:db8:0:1::9\c$ ()

The error message is:

System error 67 has occurred. The network name cannot be found.

Consider the following scenario:

• You have a server that runs the Unisys MCP operating system on a network.
• On this network, the credentials that users use to access the MCP server differ from the logon credentials that they use to log on to the domain.
• A user accesses a network share on the Unisys MCP server by using a Windows Vista-based client computer.
• To access this network share, this user types the Uniform Naming Convention (UNC) path of the MCP server.

In this scenario, Windows Vista does not enumerate the share list on the server.

However, if the user accesses a network share on the Unisys MCP server by typing the Uniform Naming Convention (UNC) path together with the share name, the user can access the network share.

For example, if the user tries to access the share by typing the following UNC path, the user cannot obtain the share list on the server:

\\ServerName

However, the user can access the share by typing the UNC path together with the share name, as in the following example:

\\ServerFQDNname\ShareName

Notes:

• In these examples, ServerName represents one of the following:
  • The FQDN name of the server
  • The IP address of the server
  • The NetBIOS name of the server
• This issue does not occur on a Windows XP-based client computer.

• Maple 11 - Windows Vista Support
  The Vista version of Maple 11 will be available in the coming weeks. Current Maple 11 users will be notified via email as soon as it is available.
  (tags: Software Compatibility )
• Samba 3.0.25 Release Works With Vista
  Good news if you run a linux server.
  (tags: Network Server Share )
• Create the perfect picture
  If you take lots of photos, and you’re running Vista, this page will be of interest.
  (tags: Photo )
• Adobe to release PostScript driver for Windows Vista
  They will release a Vista compatible driver for PostScript printers in July.
  (tags: Drivers Compatibility )
• Gates: 40 million Vista copies sold
  Selling twice as fast as Windows XP, 40 million copies sold as of last week.
  (tags: PR Sales )
• How To Run TivoToGo 2.4 on Windows Vista
  The title says it all. TivoToGo 2.4 is not Vista compatible, but if you follow these steps, they claim it will run.
  (tags: Tivo Compatibility )
• Windows Vista Client Monitoring MP is now available
  If you’ve got a Windows Server 2003 and you want to monitor the health of your Vista clients, here’s your ticket.
  (tags: Server Client Monitor Health )
• Aero and battery life
  Nick at the Windows Vista Blog comments on the recent ‘Aero kills your battery’ hoopla. He says though it’s hard to measure accurately, they estimate it uses 1-4% more battery, which they consider a fair trade-off for what Aero offers.
  (tags: Aero Battery )

Good news if you run a linux server. Keep reading →

Consider the following scenario. On a Windows Vista-based computer, you try to move a read-only file or a read-only folder from a shared folder. This shared folder is located on a Microsoft Windows 98 Second Edition (SE)-based computer. In this scenario, you may receive an error message that resembles the following:

Destination Folder Access Denied
You need permission to perform this action

After you click Retry or Cancel, you press F5 to update the screen. Then, you find that the file or the folder has been copied instead of moved.

Consider the following scenario. You create a custom application on a computer that is running Windows Vista or Microsoft Windows Server 2003 with Service Pack (SP1) or a later version. The custom application opens a file on a network share for write access. Additionally, the custom application uses the WriteFile function to write data to the file. When you run the custom application, you experience the following symptoms:

• The WriteFile function returns an error message.
• The WriteFile function returns a value of 0 (zero) for the lpNumberOfBytesWritten parameter.

You expect that the write operation failed and that no data is written to the file. However, you find that some data is successfully written to the file.

The following is an example of a scenario in which you experience this behavior.

• The custom application opens a file for an unbuffered write operation. The WriteFile function extends the file.

  Note: In certain cases, the write operation may be unbuffered even though the application does not specifically set the FILE_FLAG_NO_BUFFERING flag when the application opens the file. For example, if you open the file for write-only access instead of for read and write access, write operations to the file are unbuffered.

• Part of the write operation fails because the disk is full. However, some disk space is freed on the server. Later parts of the write operation are successfully completed.

In this scenario, the following results occur:

• The file contains blank spaces.
• The WriteFile function returns a “STATUS_DISK_FULL” error message.
• The value of the lpNumberOfBytesWritten parameter is set to 0 (zero).