cpuguru's questions

I'm creating a new Virtual Switch under Hyper-V on a Windows 2016 Server.

When I go to create a Virtual Switch under Hyper-V on Windows Server 2016, I have to select the NIC port that it will be using. Unfortunately, Hyper-V shows you the "Interface Description" in the drop-down for which NIC to use rather than the "Name". As you can see below, it's rather confusing as the NIC "Name" numbers (which match the port numbers on the back of the server) do not match the number that's auto-assigned in the "Interface Description" field.

I'd like to change the InterfaceDescription setting so that it aligns with the NIC port # so that the NIC I'm selecting in the drop-down for Virtual Switch creation matches up with the NIC number.

Looking at the registry settings, the description for all (4) of the NICs is just "Broadcom NetXtreme Gigabit Ethernet". It looks like Windows is nonsensically attaching a #2, #3 & #4 to the end of the Description names.

Any way to rename the InterfaceDescription for each NIC so that NIC1 matches up with "Broadcom #1", NIC2 matches up with "Broadcom #2" etc?

Below are the results of a PowerShell get-NetAdapter command.

PS C:\Users\Me> get-netadapter

Name -- InterfaceDescription

---- --------------------

NIC4 --- Broadcom NetXtreme Gigabit Ethernet #3

NIC3 --- Broadcom NetXtreme Gigabit Ethernet #4

NIC2 --- Broadcom NetXtreme Gigabit Ethernet

NIC1 --- Broadcom NetXtreme Gigabit Ethernet #2

We're looking for a non-RAID SAS Host Bus Adapter to connect a tape drive to our Dell PowerEdge server. Shopping around online for an LSI 9300-8e we see models listed as just "9300-8e" and models listed as "9300-8e SGL".

What's the SGL stand for?

I've been running CentOS 6.2 as a VM under Hyper-V on my Windows Server 2008 R2 system.

If I run "uname -r" it shows my current Linux version as "2.6.32-220.4.1.el6.x86_64"

A while ago, I did a software update and included in the update was a kernel update. When I rebooted the Linux VM, it came up with a kernel panic message and would not continue. I figured out that if I pressed the space bar during boot and selected the old (original) Linux kernel version, the system would boot fine.

I did some Googling and it I found a site that explains that the Linux Integration Services code needs to be recompiled for the kernel that you're running. Since I can't boot into that kernel, I'm not sure how that is even possible.

More Googling got the following site - http://support.microsoft.com/kb/2387594/de - which says I need to install Dynamic Kernel Module Support - DKMS (which I did) but when I follow further in the instructions it references a "dkms.conf" file which doesn't exist. Creating a blank one doesn't work either as attempting to run the "dkms add -m linuxic -v 3.2" command (I'm running Linux Integration Services 3.2) comes back with "Error! Bad conf file."

Any clues as to how to fix the issue so I can keep my Linux kernel up-to-date on CentOS 6 running the Linux Integration Services 3.2 drivers?

I inherited a Windows Server 2003 R2 virtual machine that was previously running under a failing Windows Virtual Server 2005. Both the C: and D: VHDs were within a few hundred megs of being full.

I created a new Hyper-V-based VM to port the old one to and edited the VHDs prior to using them by expanding them both by 10Gigs.

The integration services install & HAL upgrade went fine but when I boot the VM, both drives were still showing as almost full still.

A quick look with Disk Management shows that they both have an extra 10Gigs of unallocated space tacked onto them.

I'm thinking an easy fix would be to simply down the Win2k3 R2 VM and attach its VHDs to another Win2k8 R2 VM running on the same Hyper-V server and use its disk management tools to extend the partitions to cover the extra 10Gigs added onto them.

Will Win2k8 R2 try to tack any additional "stuff" (drive signatures or the like) onto the VHDs that would prevent the Win2k3 R2 VM from functioning? I'd hate to purchase a 3rd party partitioning utility if I can do things with stuff already in-house.

Should I deselect the "Synchronize with an Internet Time Server" checkbox under the VM's "Date and Time -> Internet Time Settings" tab if the "Time Synchronization Service" for a Hyper-V-based Virtual Machine is enabled?

One of the Integration Services that Hyper-V provides is the Time Synchronization Service, which can be enabled/disabled by going to a VM's Settings->Integration Services setting in the Management section. I believe this is checked by default.

When you install a Windows Server 2008 OS in a VM on the Hyper-V server, it comes with the "Synchronize with an Internet Time Server" option set, pointing to "time.windows.com".

I'd think that if the parent Hyper-V server is set to one time server, and the child VM is pointing to a different time server, there would be a momentary blip if the two are not spot on with their times when the synchronization services run.

So the question is, which time sync service should I use? I'm assuming not both. And what is the advantage of one over the other?

Note: This question assumes that the machines are not joined to a domain. If they were, the machines would also try to update their time against the domain controller with the primary domain controller role too, right?

Thanks!

I set up Windows Server 2008 (x64) and installed the WebDAV extension to IIS 7 (also x64) and created a WebDAV share. I also created a self-signed certificate and enabled HTTPS on the box - requiring HTTPS to connect to the WebDAV share.

I can connect to the system via Vista and connect to the "network folder" just fine. I'm able to connect, create and delete files and folders.

Trying to connect via Mac OS-X, however, I can connect to the WebDAV share, but I only have read-only access. I can't create or delete any files and folders, even though I'm signed in with the same username/password that I used on the Vista box.

What am I missing?

*Update 2008/09/17 - Feedback from a colleague is that Mac OS-X refuses to open as Read/Write unless it sees a WebDAV 2.0 server that supports LOCK methods (RFC 2518)? Investigating that now...

Now that Win2k8 with SP2 ISO's are available for download, I'm installing a new Win2k8 Std SP2 VM on my Win2k8 RTM Hyper-V host machine.

If I "Insert Integration Services Disk" on the new SP2 VM from my non-SP2 host machine, would I be introducing old "Integration Services" drivers on the SP2 VM?

I have a few distribution lists running in "Subscriber Only" mode, meaning that only somebody who is subscribed to the list (or on the Whitelist) can post to the list.

Some spammers have discovered the lists and are spoofing reply-to addresses of people on the list.

I've configured the Anti-spam settings to tag the messages matching "Weight20" in the headers with a {This is SPAM} message. It tags messages to users who have an account on the server just fine, but it's not flagging the mail going to the distribution lists.

Is SmarterMail bypassing List traffic? If so, is there a way to weed out these List-bound messages?