similar to: why I use chrome on CentOS

> On Sep 2, 2015, at 1:36 PM, zep <zgreenfelder at gmail.com> wrote: > > > > On 09/02/2015 03:12 PM, Wes James wrote: >> I use chrome on CentOS because I wrote a web socket web app and I can only get chrome to work properly with web sockets. >> >> I have a local web app created with erlang. It works like ms sccm to wake, freeze/thaw deepfreeze PCs and

On 09/02/2015 03:12 PM, Wes James wrote: > I use chrome on CentOS because I wrote a web socket web app and I can only get chrome to work properly with web sockets. > > I have a local web app created with erlang. It works like ms sccm to wake, freeze/thaw deepfreeze PCs and can update windows/mac/linux boxes when they need updates for some student computers labs and department/college

On 09/02/2015 12:40 PM, Wes James wrote: > >> On Sep 2, 2015, at 1:36 PM, zep <zgreenfelder at gmail.com> wrote: >> >> >> >> On 09/02/2015 03:12 PM, Wes James wrote: >>> I use chrome on CentOS because I wrote a web socket web app and I can only get chrome to work properly with web sockets. >>> >>> I have a local web app created with

Hello Folks, We're using Samba as AD servers along with Windows AD Servers (2008R2 FL). We also use SCCM (Current Branch) that is dependent on AD for lab deployments (Windows 10). Currently, SCCM (current branch) supports 2008R2 FL, but for how long??? Samba does not support 2012R2, 2016, 2019 FL. We'd like to remove the Windows Servers from our AD infrastructure, but would also like

Spike White, Sent: Saturday, December 27, 2014 4:32 AM > > Luke, I have considerable experience with this. We use WDS at work > for PXE (MS-centric shop). I use pxelinux at home. > > I've got WDS working in our test lab w/ UEFI. As you state, it strongly > wishes to do proxyDHCP (port 4011). More on this in a bit. > > It's quite common to segregate the DHCP

Thanks for your email. Yes it does provide some insight into why I could hack a Linux DHCP server into providing enough PXE boot information for PXE 3 clients but PXE 2.1 were happy (ROMs under many circumstances need to use proxy dhcp 4011 - as documented by IBM on the link I shared earlier). It appears only the most latest Dell business systems have EFI 64 support, and the best you can expect

This got me closer, but it got to "Encapsulating winpe.wim..." and never went through the rest of the way. Ultimately PXELINUX apparently timed out and the machine rebooted. Here is relative portion of pxelinux: LABEL SCCM OSD Boot MENU LABEL ^2. SCCM OSD Boot com32 linux.c32 append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wim TEXT HELP

Hello, I would like to know if there are any resources (success stories, comparisons, blogs...) regarding the use of puppet as a substitute to SCCM in Windows platforms. Would also love to hear success stories from Windows administrators using puppet. I''m somewhat skilled with puppet but not with SCCM, so I don''t even know if the scope of the products is really similar.

On Fri, Sep 11, 2015 at 3:19 PM, Dario Lesca <d.lesca at solinos.it> wrote: > the result. # du -sc /* /.??* --exclude /proc|sort -n 0 /.autofsck 0 /.autorelabel 0 /misc 0 /net 0 /sys 4 /cgroup 4 /media 4 /mnt 4 /selinux 4 /srv 8 /opt 16 /home 16 /lost+found 16 /tmp 112 /root 188 /dev 7956 /bin

G'day All, We are trying to set up SCCM-5.0. Our AD test is Samba-4.8.5. SCCM requires schema changes, and Samba is rejecting these. Anyone tackled this? Ideas on how to proceed? The output thrown by the SCCM exe (extadsch.exe) is: Microsoft System Center Configuration Manager v5.00 (Build 8634) Copyright (C) 2011 Microsoft Corp. Failed to extend the Active Directory schema. Your

On Fri, Aug 29, 2014 at 8:01 PM, Spike White <spikewhitetx at gmail.com> wrote: > But chain-loading into WinPE would be useful too. > In order to use "wimboot", I have to use ./efi64/com32/modules/pxechn.c32 > to chain-load into ipxe? As so: pxechn.c32 contains BIOS-only code and is not going to work in any EFI environment. > LABEL WinPE > MENU LABEL

Hey guys, I'm trying to echo my password into some commands inside of a bash script. But I think I'm going about it incorrectly. Here's the top part of my script: #!/bin/bash pub="~/.ssh/id_rsa.pub" dps_pass="my_pass" ssh="/usr/bin/ssh" scp="/usr/bin/scp" for i in 10.10.10.2{5,6} do echo "xfring key up" echo $dps_pass | $scp $PUB

> Date: Thu, 25 Dec 2014 07:07:52 +0000 > From: Luke Ledgerd <luke.ledgerd at niteco.se> > To: "syslinux at zytor.com" <syslinux at zytor.com> > Subject: [syslinux] Chain-loading from WDS to PXELinux on a different > tftp server > Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se> > Content-Type: text/plain;

> Date: Fri, 29 Aug 2014 13:02:10 +0100 > From: Michael Brown <mcb30 at ipxe.org> > To: Jason Jones <jason.s.jones at convergys.com>, "syslinux at zytor.com" > <syslinux at zytor.com> > Subject: Re: [syslinux] PXE booting WinPE with UEFI architecture > Message-ID: <54006BC2.3090703 at ipxe.org> > Content-Type: text/plain;

John, thank you for replying. On 12/03/2014 03:21 PM, John R Pierce wrote: > On 12/3/2014 12:47 PM, g wrote: >> wireshark text file loaded at; >> >> http://pastebin.com/rCU0CC10 > > some device on your network has the MAC address 00:0f:fe:8f:8f:23 > which Wireshark is calling PartedMagic for unknown reasons. see my new paste at; http://pastebin.com/8vBxnUSf

Hey guys, We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off anything you want to including PXELinux. The stuff I was talking about before with PXELinux not working in

On Sat, Dec 20, 2014 at 6:28 AM, Jonathan Billings <billings at negate.org> wrote: > I suggest keeping your system up to date before trying to track down > whatever problems you're having. I was able to remove firefox from the equation and reproduce the problem using curl NON working URL [igor at localhost ~]$ ping www.iquaid.org PING www.iquaid.org (208.97.177.112) 56(84) bytes

On Dec 25, 2014 2:11 AM, "Luke Ledgerd" <luke.ledgerd at niteco.se> wrote: > > Hey guys, > > We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off

Hi, I have a Microsoft application (SCCM) which I need to grant access to a samba share, however the service which reads the files can only authenticate using the computer account, there is option to configure it to use a domain account. Is there any way to grant a computer account access to a share? On windows I can simply add computer$ to the permissions but this doesn't seem to be

On 03/26/2015 10:40 PM, Bob Hepple wrote: > Boris Epstein <borepstein at ...> writes: > a set of scripts/utilities for automatically >> starting and running headless (no X11) VM's using VirtualBox omn a CentOS 6 >> server. VNC/RDP access to the VM's would be fine. > vagrant? > > _______________________________________________ > I'm unfamiliar with