search for: ws2012

Hi, I have quite a difficult task to solve. I need to migrate from Samba 3 to WS2012 AD. I know the steps are Samba 3 to Samba 4 to WS2008 to WS2012R2. I managed to upgrade Samba 3 PDC to Samba 4 AD, but I am not able to move roles to WS 2008 as I have some DNS related problems. Is there any howto regarding Samba 4, DNS and Active Directory? Better, I would appreciate some lin...

Hi, I have quite a difficult task to solve. I need to migrate from Samba 3 to WS2012 AD. I know the steps are Samba 3 to Samba 4 to WS2008 to WS2012R2. I managed to upgrade Samba 3 PDC to Samba 4 AD, but I am not able to move roles to WS 2008 as I have some DNS related problems. Is there any howto regarding Samba 4, DNS and Active Directory? Better I would appreciate some lines d...

...update > utility, then it shouldn't be too complicated. Firs of all you will need > to obtain the Windows kernel version by reading the following Registry > key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it > 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > string from the same hive will give you information about the platform > bitness. Next you need to go through inf files, and find "DriverVer" > string, like this one . taken from from vioscsi.inf > > DriverVer=08/01/2015,62.72.104.10800...

...en it shouldn't be too complicated. Firs of all you will need >>> to obtain the Windows kernel version by reading the following Registry >>> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" >>> string from the same hive will give you information about the platform >>> bitness. Next you need to go through inf files, and find "DriverVer" >>> string, like this one . taken from from vioscsi.inf >>> >>&g...

...ility, then it shouldn't be too complicated. Firs of all you will need > > to obtain the Windows kernel version by reading the following Registry > > key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it > > 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > > string from the same hive will give you information about the platform > > bitness. Next you need to go through inf files, and find "DriverVer" > > string, like this one . taken from from vioscsi.inf > > > > DriverVer=08...

...plicated. Firs of all you will need > > >>> to obtain the Windows kernel version by reading the following Registry > > >>> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it > > >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > > >>> string from the same hive will give you information about the platform > > >>> bitness. Next you need to go through inf files, and find "DriverVer" > > >>> string, like this one . taken from from vioscs...

Hello, We're running Centos 7 with samba 4.7.1 and we have an AD on WS2012 R2, so all users and groups are already created on the AD. The idea is to logon with the credential from de AD to the samba file server. We configured the smb.conf, acording to the samba wiki, so this is the result: [global] security = ADS workgroup = MYDOMAIN realm = MYD...

...es Syue ???: >> I can't say for sure but I *think* each time the client is windows server 2012. > > Looks good :) If run this script[1] to test multiple dialects, found only > SMB3_00 and SMB3_02 has this "(sign_algo_id=1)", and per doc[2] it could > be happend with ws2012 and ws2012r2. This *is* 2012 r2. The protocol version it negotiates is shown by smbstatus on samba server, it is SMB3_02. More modern workstations negotiate SMB3_11. > Perhaps some kind of services, like antivirus scan LAN, or printer access, > access attempts to samba server via guest or...

...s > will > > only send options listed in the Parameter Request List in the > DHCPDISCOVER > > packet. > > > > One could make a cleaner setup by creating a BIOS PXEClient vendor class > > and putting their options within a policy too. > > I haven't tried WS2012 yet but PXELINUX will parse DHCP option 43 > (vendor-specific information) nicely and I have encapsulated 210 > inside 43 successfully (can't recall if I tried WS2008R2 and/or > ISC-DHCPd but I did at least one). > > The one oddball missing from your recipe is the UEFI x86 system...

I've found a way to support PXE booting both UEFI and BIOS architectures with Windows Server DHCP. This method uses a feature introduced in WinServer 2012: DHCP policies. First, in the the DHCP console, at the IPv4 root of the server, create a vendor class named PXEClient (UEFI x64) with the following value: PXEClient:Arch:00007 Then create your configuration for your BIOS clients in your

...39;t be too complicated. Firs of all you will need > >>> to obtain the Windows kernel version by reading the following Registry > >>> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it > >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > >>> string from the same hive will give you information about the platform > >>> bitness. Next you need to go through inf files, and find "DriverVer" > >>> string, like this one . taken from from vioscsi.inf > >...

On Wed, Oct 28, 2015 at 12:10:19PM +1100, Vadim Rozenfeld wrote: > > > > To sum up, the packaging and naming policy of the virtio-win rpm and the > > > > virtio-win iso therein are different and neither is clear. Hardcoding > > > > the policy in v2v without actually knowing it appears risky at best. > > It's due to historical reasons mostly. The best

...t what virt-v2v already does. This is good information: > First of all you will need > to obtain the Windows kernel version by reading the following Registry > key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it > 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" > string from the same hive will give you information about the platform > bitness. Next you need to go through inf files, and find "DriverVer" > string, like this one . taken from from vioscsi.inf > > DriverVer=08/01/2015,62.72.104.10800...

...gt; > This is good information: > >> First of all you will need >> to obtain the Windows kernel version by reading the following Registry >> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it >> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" >> string from the same hive will give you information about the platform >> bitness. Next you need to go through inf files, and find "DriverVer" >> string, like this one . taken from from vioscsi.inf >> >> DriverVer=08/01/2...

I''d like to be able to use OpenGL on a remote Windows box (WS2012), so I''ve been experimenting with Xen for the past few days. Most of the work-throughs for 3D acceleration with Windows that people post/blog are for local machines, that is the display is shown on the local screen. Is it possible to forward accelerated video through VNC or RDP w...

...on 210 (path prefix). Microsoft DHCP servers will > only send options listed in the Parameter Request List in the DHCPDISCOVER > packet. > > One could make a cleaner setup by creating a BIOS PXEClient vendor class > and putting their options within a policy too. I haven't tried WS2012 yet but PXELINUX will parse DHCP option 43 (vendor-specific information) nicely and I have encapsulated 210 inside 43 successfully (can't recall if I tried WS2008R2 and/or ISC-DHCPd but I did at least one). The one oddball missing from your recipe is the UEFI x86 systems that are not 64 bit....

...FI clients because Microsoft >> DHCP >> > server does not send option 210 (path prefix). Microsoft DHCP servers >> will >> > only send options listed in the Parameter Request List in the >> DHCPDISCOVER >> > packet. >> >> I haven't tried WS2012 yet but PXELINUX will parse DHCP option 43 >> (vendor-specific information) nicely and I have encapsulated 210 >> inside 43 successfully (can't recall if I tried WS2008R2 and/or >> ISC-DHCPd but I did at least one). >> > -- Alexandre Blanchette <blanalex at gmail...

...c virtio-win drivers update utility, then it shouldn't be too complicated. Firs of all you will need to obtain the Windows kernel version by reading the following Registry key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx" string from the same hive will give you information about the platform bitness. Next you need to go through inf files, and find "DriverVer" string, like this one . taken from from vioscsi.inf DriverVer=08/01/2015,62.72.104.10800 This string contains bui...

Hi, I am the guy who puts together the virtio-win package for Red Hat. I recently took over this role so I'm still in learning mode. On Wed, Oct 28, 2015 at 04:15:06PM +0200, Yan Vugenfirer wrote: >> On 28 Oct 2015, at 13:53, Roman Kagan <rkagan@virtuozzo.com> wrote: >> On Wed, Oct 28, 2015 at 12:10:19PM +1100, Vadim Rozenfeld wrote: >>>>>> To sum up, the