search for: win81

...ject: Windows PE booting without chainloading ipxe I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. http://ipxe.org/wimboot MENU LABEL Windows 8.1 Enterprise PE Rescue (wimboot) com32 linux.c32 /wimboot APPEND initrdfile=/windows/win81/bootmgr,/windows/win81/boot/bcd,/windows/win81/boot/boot.sdi,/windows/win81/sources/boot.wim The initrdfile= is supported in Syslinux from patches to5.03 onwards on the mailing list but it seems wimboot has moved on from last year so the documentation on various blogs saying this can be done is ob...

...untu 14.04, samba 4.2 installed from source. > > > > On Ubuntu and samba 4.1.17 (installed also from source) all works fine. > > I don't have 4.2 in production at work. But I tried in my test > environment here at home (2 DCs - both 4.2.0): > > RDP > Win10 -> Win81: OK > Win10 -> Win7: OK > Win81 -> Win7: OK > Win7 -> Win81: OK > > For testing I created a new user (no home drive, no logonscript, no > server base profile, etc.) in AD and allowed the domain group "domain > users" to login via RDP on all three machines. &...

I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. http://ipxe.org/wimboot MENU LABEL Windows 8.1 Enterprise PE Rescue (wimboot) com32 linux.c32 /wimboot APPEND initrdfile=/windows/win81/bootmgr,/windows/win81/boot/bcd,/windows/win81/boot/boot.sdi,/windows/win81/sources/boot.wim The initrdfile= is supported in Syslinux from patches to5.03 onwards on the mailing list but it seems wimboot has moved on from last year so the documentation on various blogs saying this can be done is ob...

Hi, i did some tests wit samba 4.2 as a ADS DC on arch linux. On a Win8.1 client i can do local logins as every user, i can login via RDP as local user, but i am not able to login as a domain user via RDP. After the loginscreen, appears "Welcome" and the mousepointer continues to spinn.... Same issue on Ubuntu 14.04, samba 4.2 installed from source. On Ubuntu and samba 4.1.17

...ainloading ipxe > > I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. > http://ipxe.org/wimboot > > MENU LABEL Windows 8.1 Enterprise PE Rescue (wimboot) > com32 linux.c32 /wimboot > APPEND initrdfile=/windows/win81/bootmgr,/windows/win81/boot/bcd,/windows/win81/boot/boot.sdi,/windows/win81/sources/boot.wim > > The initrdfile= is supported in Syslinux from patches to5.03 onwards on the mailing list but it seems wimboot has moved on from last year so the documentation on various blogs saying this can be...

...t; >>>> On Ubuntu and samba 4.1.17 (installed also from source) all works fine. >>> >>> I don't have 4.2 in production at work. But I tried in my test >>> environment here at home (2 DCs - both 4.2.0): >>> >>> RDP >>> Win10 -> Win81: OK >>> Win10 -> Win7: OK >>> Win81 -> Win7: OK >>> Win7 -> Win81: OK >>> >>> For testing I created a new user (no home drive, no logonscript, no >>> server base profile, etc.) in AD and allowed the domain group "domain >>&gt...

...to spinn.... > > Same issue on Ubuntu 14.04, samba 4.2 installed from source. > > On Ubuntu and samba 4.1.17 (installed also from source) all works fine. I don't have 4.2 in production at work. But I tried in my test environment here at home (2 DCs - both 4.2.0): RDP Win10 -> Win81: OK Win10 -> Win7: OK Win81 -> Win7: OK Win7 -> Win81: OK For testing I created a new user (no home drive, no logonscript, no server base profile, etc.) in AD and allowed the domain group "domain users" to login via RDP on all three machines. I can't see a problem here. *...

...rce. > > > > > > On Ubuntu and samba 4.1.17 (installed also from source) all works fine. > > > > I don't have 4.2 in production at work. But I tried in my test > > environment here at home (2 DCs - both 4.2.0): > > > > RDP > > Win10 -> Win81: OK > > Win10 -> Win7: OK > > Win81 -> Win7: OK > > Win7 -> Win81: OK > > > > For testing I created a new user (no home drive, no logonscript, no > > server base profile, etc.) in AD and allowed the domain group "domain > > users" to log...

...the password (the "setpassword" from user command doesnt work, maybe simply --password?) * creating a computer with a given machine password (maybe simply --password,too ?) * reading the machine password from AD (there i found some old variant which didnt work, tested with Win81-clients) * perform an offline join with a previously given/read-from-ad machine password Is this possible, some examples anywhere? Tfh! Oliver

...create mask = 0660 > directory mask = 0770 > force group = Family I've started exactly this smb.conf here on my Fedora 21 (Samba 4.1.17) PC. I've only replaced eth0 with my device name and the IP stuff. When I try to copy > 4 GB ISO files from/to this share to/from my Win81 laptop, I have a constant transfer rate of ~110 MB/Sec: http://picpaste.com/screenshot-IXV2zgmI.png Your low transfer rates seem to have a different reason (HDD performance, filesystem or many other things). Regards, Marc

Here my samba conf file: [global] ??? workgroup = MYGROUP ?? ?server string = Samba Server Version %v ? ??? interfaces = lo eth0 x.x.x.x/x #my ip and mask ?? ?hosts allow = 127. 10.0. ??? log file = /var/log/samba/log.%m ?? ?max log size = 50 # ----------------------- Standalone Server Options ------------------------ ?? ?security = user ?? ?passdb backend = tdbsam #

...Ubuntu 14.04, samba 4.2 installed from source. > > > > On Ubuntu and samba 4.1.17 (installed also from source) all works fine. > > I don't have 4.2 in production at work. But I tried in my test > environment here at home (2 DCs - both 4.2.0): > > RDP > Win10 -> Win81: OK > Win10 -> Win7: OK > Win81 -> Win7: OK > Win7 -> Win81: OK > > For testing I created a new user (no home drive, no logonscript, no > server base profile, etc.) in AD and allowed the domain group "domain > users" to login via RDP on all three machines. &g...