MDT 2013 stalls during first boot into OS
I just built a new MDT 2013 server (on 2012 R2) and am attempting to deploy Windows 7 from it via litetouch. I've been working with MDT 2010 for several years so I am pretty familiar with how it works and just about everything is fine with 2013 except
for one small issue. When the sequence boots into Windows 7 for the first time, it just sits there at the desktop and nothing happens. This happens every time and performs the same on virtual and physical machines. All I have to do is reboot
the machine and the task sequence will pick right up where it left of and finish everything correctly.
I have found similar reports that seem to be resolved by adding pauses to either the ltibootstrap, litetouch, or ztiutility scripts to give the machine additional time to initialize, but none have worked for me. The only seemingly relevant log entry
comes from the BDD file. The last entry is:
<![LOG[RUN: regsvr32.exe /s "C:\Users\wdsbuild\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="17:47:46.000+000" date="03-25-2014" component="LiteTouch" context="" type="1"
thread="" file="LiteTouch">
<![LOG[FAILURE (Err): -2147024770 0x8007007E: CreateObject(Microsoft.BDD.Utility) -]LOG]!><time="17:47:46.000+000" date="03-25-2014" component="LiteTouch" context="" type="2" thread=""
file="LiteTouch">
I question the relevance of this entry because I don't actually have to manually register the dll to get it to work again. Everything else in the BDD and SMSTS logs looks fine and don't appear to give any indication of what is going on.
I have also attempted to add an additional restart to the task sequence immediately following the restart that is initiated after the OS has been laid down, but since the task sequence doesn't start after that first autologin, it doesn't execute.
Thoughts?
+1 on the drivers. I have rarely seen this, never able to reproduce in a consistent manner.
Here is the process:
* MDT places a hook within the unattend.xml file applied to the operating system. It calls the script LTIBootStrap.vbs. This happens in OOBE setup. If you did not sysprep or skiped OOBE setup this step may fail.
* LTIBootStrap.vbs calls "Litetouch.wsf /Start" to install itself in the start/run after reboot into the full OS.
IT *might* be possible that there is some other application hooked in to run at logon that is preventing MDT from running. Using autoruns.exe from sysinternals could help in debugging.
Alternatively, you could set HIDESHELL=YES in your cs.ini file. When this is set, MDT will add it self in the registry as a "run" command rather than within the "startup" group in the shell.
Keith Garner - keithga.wordpress.com
Similar Messages
-
[solved] Large number of services enabled during first boot
I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
Any ideas as to what might be causing this?
Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
getty.target.wants:
* [email protected]
multi-user.target.wants:
* [email protected]
* iptables.service
* remote-fs.target
* sshd.service
sysinit.target.wants:
(none)
Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
default.target.wants:
* systemd-readahead-collect.service
* systemd-readahead-replay.service
multi-user.target.wants:
* dhcpcd.service * krb5-kpropd.service
* fstrim.service * nscd.service
* ftpd.service * rsyncd.service
* gpm.service * systemd-journal-upload.service
* ip6tables.service * systemd-networkd.service
* krb5-kadmind.service * systemd-resolved.service
* krb5-kdc.service
sockets.target.wants:
* krb5-kpropd.socket * systemd-journal-remote.socket
* rlogin.socket * talk.socket
* rsh.socket * telnet.socket
* rsyncd.socket * uuidd.socket
* sshd.socket
sysinit.target.wants:
* dm-event.service
* systemd-timesyncd.service
system-update.target.wants:
* systemd-readahead-drop.service
Explicitly installed packages:
dhcpcd iputils procps-ng systemd-sysvcompat
diffutils linux-grsec psmisc tar
dnsutils logrotate reflector vim-systemd
file mlocate rsync wget
gradm mtr s-nail which
grub openssh screen whois
inetutils pacman
Last edited by tazmanian (2014-09-10 23:11:42)+1.
Here is the ports these services are listening:
$ ss -tpl
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 *:llmnr *:*
LISTEN 0 128 *:ssh *:*
LISTEN 0 128 :::llmnr :::*
LISTEN 0 128 :::19532 :::*
LISTEN 0 128 :::tell :::*
LISTEN 0 128 :::ssh :::*
LISTEN 0 128 :::telnet :::*
LISTEN 0 128 :::login :::*
LISTEN 0 128 :::shell :::*
LISTEN 0 128 :::rsync :::*
LISTEN 0 128 :::git :::* -
Kernel crashing during first boot on VirtualBox
I'm trying to get install Arch Linux on VM running on my Windows 7, I set up the machine and everything else that was in the guide on wiki, but during first boot, I get kernel error and machine freezes.
This is screenshot of error:
http://i.imgur.com/msTUERH.png
I'm new to Linux so I might have missed something obvious, don't be too harsh on me please
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --Mhm, I only have to suggestions (I am not a kernel-pro though):
Enable PAE/NX at the "System -> Processor" tab in the vbox configuration
If that does not work disable it and try to reconfigure the vm with minimal settings in virtualbox. For example, disable audio, networking, usb, 3d etc... and see wether your machine crashes or not.
Last edited by Resauce (2014-12-08 07:12:47) -
ThinkStation S20 shuts down during first boot
Hi,
I've recently purchased S20 (4157), one starnge thing I've noticed:
When machine was unplugged from mains socket and plugged back in, if I press power button the machive will start booting up but will shut dow after approx 10 sec.
Some details:
- No Lenovo startup screen shown, the screen remains black and no signal from graphics card
- No beeps
- Sonds like the HD was being tested just before the shutdown
Then if I press power button again, the PC starts normally.
This happens if power setting 'After Loss of Power' in BIOS configured to 'Stay Off'.
My question: is this normal behavior? I've recently updated BIOS to the latest version.
Also, if the BIOS power setting is changed to 'Stay On', the machine will turn itself on as soon as it's plugged into mains, and will boot normally. This looks pretty normal to me.
Thanks!
Solved!
Go to Solution.This is normal. BIOS needs to "work some magic" so to speak when AC power is first applied to prepare for normal boot operation.
-
How to disable Internet from running when users first boots into Windows 8.1 Pro
Recently added Windows 8 into our environment, everything works fine except the IE 11 always pops up at initial logging. Is there a way to disable this w/ Group Policy?
Thanks in advance.
Roget LuoHi,
Did you mean that once users first log on Windows 8.1 and IE 11 pops up? Did this issue happened after logging off then logging in and shutting down the PC then restarting to login?
What’s the detailed information about the pop-up? The screenshot would be more helpful for us to determine the issue.
We can check if there is any logon script or task schedule configured in your environment.
For further help you, please provide more information about how you deploy Windows 8.1.
Meanwhile, please help to collect the boot trace for further research.
How to collect a good boot trace on Windows 7
http://blogs.technet.com/b/jeff_stokes/archive/2012/09/17/how-to-collect-a-good-boot-trace-on-windows-7.aspx
Once down, please upload the .etl file into SkyDrive or Similar ones and share the public link here for our research.
Look forward to your response.
Kate Li
TechNet Community Support -
[Boot Camp] Can't send a Ctrl-Alt-Del during first boot!
Hello,
I just Installed WIndows Server on iMac using Boot Camp. It requires that once the password is set (per Group Policy on Windows Server PCs), I'll have to login by pressing Ctrl-Alt-Del (this is my first time login) and i'm unable to figure out how can it be done! I know that there is a discussion running everywhere about the PC equivalent "Del" key on iMac. I have tried the following -
1. Ctrl-Alt-Del (Del is actually Backspace) : Doesn't work
2. Ctrl-Alt-Del (Fn Key pressed down - that makes it delete) : Doesn't work
I read somewhere that mapping a key differently should work. But i'm unsure of the process and i also understand that i'll have to do it from the OS. In my case, i'm not logged in yet! Is there someone who can help me in this regard?
Maybe, I can use backspace and delete functions on iMac but i'm looking for a equivalent "Delete" KEY and not Delete FUNCTION to Login. If you can point me to a existing thread or post solutions/thoughts, i'll be thankful.
Sivarama Krishnan(kvsrkrishnan)The retail OS X 10.6.3 DVDs unlike your OEM DVD does have a complete set of drivers for $29 w/o having to deal with questionable bitorrent.
Microsoft EOL'd XP and Vista SP1.
Your Mac has Intel Thunderbolt and you don't see Apple doing backward compatibility. You can't run 10.5 on new Mac. So yes it comes with those limitations, but XP is also 20x more vulnerable, IE9 is more secure and XP has not kept up with the latest hardware, besides which I don't see a place or need for a 32-bit OS, any platform today. -
MDT 2013 - Litetouch.wsf continues to run at login
Hi all! I recently imaged a server with MDT 2013 and after it booted into Windows one of the applications I configured to install crashed and we ended up with an incomplete deployment. In this case this was fine and we moved on, but now every time a user
logs in something is attempting to launch the Litetouch.wsf script. I ran LTICleanup manually and removed the MININT folder, but I continue to get a pop-up at login that Litetouch cannot be found.
I have tried every registry key I am aware of HKCU and HKLM Run and Runonce keys and also checked the startup folders for every user. What is calling Litetouch? How can I stop this from happening? Thanks!Hi Matt McNabb,
I guess you must create some script execute Task Sequence in your deploy task and it not complete because the deploy error occur, you can delete this script then try again,
this forum is mainly for WDS related issue it’s not the best place to talk about the MDT issue, there have a specific MDT support forum you can post in MDT support forum and get the MDT expert further support.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
Thanks for your understanding and support.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Windows 8.1 Copyprofile Issue (SCCM 2012R2 MDT 2013)
Hi,
We're experiencing several issues during creation of our base Windows 8.1 image.
Running SCCM 2012 R2 with MDT 2013 Integration.
Admin user customizations (a couple of simple UI settings and a wallpaper) are done to the Windows 8.1 image in audit mode. The OS is then sysprepped and captured via SCCM capture media.
We are using a standard MDT integrated task sequence for a zero touch deployment.
We are adding copyprofile to unattend.xml in the relevant MDT settings package.
Sequence completes without error and customizations appear in the image.
However, desktop IE11 immediately crashes unless it's run as administrator. This can be fixed by disabling protected mode (not ideal)
All Metro/Modern apps (including IE) are also initially broken. They immediately crash and drop you back to the desktop when you run them.
After a reboot the modern/metro apps (apart from IE) seem to reinstall and function correctly.
Has anyone else got copyprofile working correctly for 8.1 in a SCCM/MDT task sequence?
thanks
JamesHi James,
We were able to work around this issue in the following way using SCCM 2012 R2. I know this is not how the process is documented or has worked previously but it is what worked for us.
1. Create an unattend.xml with the copy profile setting (and whatever other settings) enabled.
2. On the image which will be captured run all of our regular steps to customize on the administrator profile (I always set administrator pw at this point to have blank pw, don't know if still required), copy that unattend.xml locally.
3. Do not run a standard capture using SCCM capture ISO, instead manually run sysprep specifying the unattend.xml. I.e. sysprep /generalize /oobe /shutdown /unattend:C:\Unattend.xml .
4. Boot to either the SCCM PXE or some other environment on that computer that has network access, and access to imagex.
5. Run an imagex capture to a network location (in our case the C: was all that was needed).
6. Import that WIM into SCCM as part of task sequence. Also added same unattend.xml used for sysprep into the task sequence to apply settings during first boot after image.
7. Validated our start menu icons and layout are there on the image.
Until the behaviour changes in Windows 8.1 or SCCM, then this should get you by. Little bit of extra work in the capture but we had positive, consistent results using this method.
Thank you! This was driving me crazy! Now it works on the first try.
Just a side note: You should not use ImageX with Windows 8.1. Create a new WinPE Bootmedia and use DISM! ImageX is outdated. -
No SATA drive after booting into Windows (BootCamp 5.0)
One of my DVD burners has failed in one of my 2008 Apple Mac Pro's. I pulled the drive out (it was PATA/IDE) and replaced with a new LG WH14NS40 Blu-Ray Burner. I had to pull the fan out (temporarily) and run a new 24" SATA cable (with right-angle connector) from one of the two extra SATA ports (on the motherboard) to the new actual SATA drive, and also install a MOLEX to SATA power connector.
I managed to get the drive installed (and working). I now at least have a Blu-Ray burner in my 2008 Apple Mac Pro (with OS X 10.8.3 Mountain Lion).
The problem seems to be with when I boot directly into Windows 8. When I boot into Windows 8, the two ports on the motherboard are disabled and the latest BootCamp 5.0 drivers don't seem to support the two SATA ports on the motherboard (they seem to be disabled). So when I boot directly into Windows, my LG WH14NS40 Blu-Ray drive disappears.
I really wish Apple would have just "done things right" from the very beginning and took the time to write decent BootCamp 5.0 drivers that supported the two SATA ports on the motherboard, so that users who need to replace their old/dying/aging PATA drives could easily replace them with SATA drives and use the two SATA ports on the motherboard.
Also it would have been nice if Apple would have taken the time to write good BootCamp 5 drivers (for Windows 8) that support booting from the two SATA ports on the 2008 Apple Mac Pro motherboard.
I've heard of many people that have tried installing RAID Controller Cards (from OWC) in their 2008 Apple Mac Pro to upgrade their four hard drive caddys from SATA II (3Gbps) to SATA III (6Gbps) but unfortunately the RAID Controller Cards don't seem to be bootable and the only option is to install a fifth (bootable) hard drive into the Apple Mac Pro and this is normally done by installing a bootable SSD drive into one of the DVD-drive bays. Unfortunately if you use a SATA SSD drive (which most SSD's are SATA) and then use one of the two SATA ports on the motherboard to connect it, then you go back to having the problem of not having a boot drive when you boot directly into Windows 8 (since there are no BootCamp 5 drivers for the 2008 Apple Mac Pro that support the two SATA ports on the 2008 Apple Mac Pro motherboard).
This seems to be a never-ending problem, and we have twelve 2008 Apple Mac Pro's (along with an office full of 2008/2009/2010/2013 Apple Mac Pro's) and we're getting extremely frustrated with Apple's lack of support in BootCamp 5.0 drivers for the 2008 Apple Mac Pro (and the two SATA ports on the mainboard).
Please fix this problem, and please update the BootCamp 5.0/5.1 drivers (for 2008 Apple Mac Pro users) and please support the two SATA ports on the Apple Mac Pro mainboard, and please make those two SATA ports on the motherboard bootable and usable in both Microsoft Windows 8 and in OS X 10.8.3 Mountain Lion. Please update the BootCamp 5.0 drivers to support the two onboard SATA ports in Windows 8 (so that my Blu-Ray burner is viewable/usable in Windows 8).Just as a follow-up, yes it does seem to be possible to get both SATA ports on a 2008 Apple Mac Pro working (in Windows 8).
You need to enable AHCI in Windows 8.
First boot into Windows 8 and then go into the windows registry (regedit) and enable AHCI in your registry.
You can do this by going to the following registry key:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci
Set the "Start" Value data to "0" (to enable AHCI in Windows).
After AHCI is enabled in Windows, then reboot your computer and now the SATA drive (connected to the ODD port) should appear in Windows (under devices).
Now the next step is to update your AHCI drivers (in Windows) to the latest Intel drivers, so that your SATA device will actually work (and work properly).
The latest Intel RST drivers can be found here: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=2306 0&ProductFamily=Software+Products&ProductLine=Chipset+Software&ProductProduct=In tel%C2%AE+Rapid+Storage+Technology+(Intel%C2%AE+RST)&lang=eng
Download the 64-bit drivers (if you are running 64-bit Windows).
After you install the latest drivers, and perform a reboot, your SATA drive should now work under windows.
You can find a long detailed thread about enabling AHCI (in Windows 7) here: http://forums.macrumors.com/showthread.php?t=760482
The thread listed above is a bit old/dated (2009?) but it does give detailed step-by-step instructions for those that want to enable AHCI (and get those two onboard SATA ports working in Windows 8 or Windows 7).
I managed to get everything working in Windows 8, and I was able to enable AHCI in Windows 8, installed the latest AHCI drivers and I'm now able to use my SATA Blu-Ray burner in my 2008 Apple Mac Pro.
Hope this helps!
-> Mark -
OSD Failure - Windows 7 - Blue Screen on First Boot in Full OS
Hi,
We are experiencing a really strange problem with our OSD which is hard to pin down. Our setup is SCCM 2012 R2 with 4 PXE enabled DP's (VMWare VMs) across 2 data centers and on seperate hosts and we are delivering Windows 7 (32 and 64) with recaptured WIM
files. Ouor deployments work fine for around a week and then they suddenly start experiencing a reboot look and blue screening at the first boot into the full OS.
This occurs on multiple different physical machines and we inject driver packages for different builds with WMI filters on motherboard as is common. The really weird part is that this will work for days then stop working. The only workaround we have is to
recapture the WIM file (we have a build and capture task sequence for this) and then it works again, even though the content and drivers are exactly the same from the same B+C task sequence. Even the windows updates are the same with no new ones. It doesn't
seem to be the drivers themselves but rather the process of DISM injecting them offline in windows PE which appears to break the registry. The last thing we see before blue screen is "Updating registry" in windows 7 boot.
These are the things we have tried are...
- Recapturing the WIM (works for around a week but not a fixed period)
- Host the WIM on a physical DP (to rule out VMWare) with only the WIM and a single driver package. Again this worked fine for a week or so.
- Built several different physical machines. All fine but when this stops, it stops for all of them
- If we remove all drivers but the LAN driver it can work but our testing has ruled out a specific bad driver as we have used different models of machine and if it was, then it would never work.
- We have set the TFTP block size to default of 1024 (we had it higher as 8192) to rule out the boot image being corrupted on download. It made no difference other than being a lot slower.
- Compared MD5 hashes for the WIM to rule out corruption.
- Removed and redistributed the WIM and drivers to different DP's (that it had never been on before)
The DISM.log on a failed device shows entries like
CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
Any advice would be greatly appreciated. This question on
Dell's forum sounds very similar.
What we are really struggling with is why would the same WIM, with the same driver package, from the same distribution point, to the same physical machine, work every day for a week the permanently break? Aaargh!
Thanks everyone,
ShaunHi,
Have this problem been resolved? How?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
MDT 2013 won't capture 8.1 image, does not boot to PE to capture
I am doing this with Server 2012 R2 and MDT 2013, and the reference machines are VMs
I initially created a deployment share for creating windows 7 and windows 8.1 reference images and capturing and deployment worked ok. After getting into some more details i customized the deployment share customsettings to make things easier and created
a separate capture share for capturing new reference images. I updated permissions on the share so my service account has access to it.
In this share i imported the windows 8.1 os files and copied the sysprep and capture task sequence i used to capture my first reference image [from the original deployment share], but when running the task sequence it reboots and just goes back into windows,
instead of windows PE to capture the image.
I copied a windows 7 capture sequence to the capture share, imported the windows 7 files and updated the task, and it rebooted into PE without a problem and copied an image. so I don't believe I have any permissions/customsettings problems with the new share.
Im not seeing any errors jump out at me in the bdd.log but I'm new-ish to going over the logs and using MDT to start with so I may be missing the obvious. I am using SMS trace and dont see any red/yellow highlites either.
In windows 7 i did have the vm in audit mode when i mapped the share as an admin and started the task sequence. In windows 8.1 i am not in audit mode [after doing some research and learning more about using MDT it did not seem necessary]
After comparing a run of the windows 7 task to windows 8 i see the boot.wim copied to the win 7 vm, but i dont see it on the win 8 vm. There is a partition created, i cant see data in it when i show hidden files.
rules for the capture share
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
Heres the last part of bdd.log. New here so I can't post a link yet, didnt know if i should post the whole thing here or not to start with.
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property PHASE is now = CUSTOM]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[--------- Script Start ---------]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[Creating startup folder item to run LiteTouch.wsf once the shell is loaded.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property BootPE is now = ]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:32:24.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="E:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = E: C:]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = CUSTOM]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentType = CUSTOM]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceDrive is now = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[SMS Task Sequencer already found on C:\MININT\Tools\X64]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">Thanks for your reply.
The pc is not in the domain when i run litetouch. It was joined after install, then i run some local gpos/scripts against it, install all of the shared printers from servers, then i put it back in a workgroup, login as the local administrator, delete the
domain profiles and guids in the registry, briefly connected back to a domain server [not with a mapped drive] to copy a couple of files, rebooted into the local admin account an ran litetouch.
After running litetouch.wsf the first time in the windows 8.1 pro vm [no changes, but manual connection] it rebooted without sysprepping or taking an image
I deleted the task sequence and created another one with "sysprep and capture" as the sequence. i made no changes to the task sequence. did all of the above, ran litetouch, and it just reboots. sysprep does not run and windows pe does not load.
if i run sysprep and boot into audit mode [as a test, since my windows 7 vm snapshot was in audit mode when it runs litetouch.wsf], then run litetouch, sysprep works, then it DID capture an image, but after that image was capture and the VM rebooted, i got
this error when loading windows 8
"windows could not complete the installation. To install windows on this computer, restart the installation" and if i hit ok it will reboot and error out again.
Haven't had any issues with that VM until now.
I reverted to my snapshot and just ran sysprep oobe w/ generalize to see how it would react
it failed, setuperr.log shows SYSPRP failed to remove apps for the current user. some searching gives me information on that and makes me think its related to adding/deleting user profiles? i dont actually use or update the apps at all, i have a deploy task
that removed most of them and customizes the start screen and those seem to work without issue.
found this as my reference: http://support.microsoft.com/kb/2769827/en-nz
Sysprep has an additional provider that is added in Windows 8 to clean appx packages and generalize the image. The provider will only work if the Appx package is a per-user package or an all-user provisioned package.
and
Resolution
The correct way of removing the package is to remove the package for the user running sysprep and also remove the provisioning. This can be done using the following Powershell cmdlets:
Import-Module Appx
Import-Module Dism
Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
if i run that i get a lot of
[unknown user]: installed
Do I just need to revise my process and start from scratch? or at least just never actually join the domain and user other profiles? thats a convenience thing so its not a big deal, really.
I have an image made in a similar way that works, but doesnt have quite all the updates/changes i wanted. It captured [at the time] fine and installs without issue
Heres an overview of what I do [i am open to some revisions on this]
-deploy windows 8 base install from MDT
-join domain, login with service account [just makes getting to some things easier]
-install office 2010 pro plus w/ sp2 [i do understand that these can be set as an MDT app but the install takes a while and i dont like waiting on it if i dont have to]
-install windows updates [no WSUs server currently, on my future to-do list, not my decision right now and i do understand the benefits of having one]
-connect to servers and install all network printers [we have so many that i dont want to wait on the drivers when we do a big roll out soon]
-install oracle software [i can get it to automate in windows 7, not 8, so i dont want to manually deal with it post-install]
-install adobe reader/java [i do understand that these can be set as an MDT app]
-leave domain, reboot, login as local admin
-clean domain profiles/registry guids
-make some local gpoedits [we dont have 8.1 enterprise and just want the start screen locked down]
-install our AV network agent
-lite touch.
any advice is appreciated -
Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast. -
MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login
Hi There,
The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
The test machine I have been using is the Surface pro 2.
The interesting part is after a failure is if I start the process over again , boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
been edited to search and apply ther split .swm files. This works well.
After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt do anything.
I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
Thank You in advance!Hi,
Thanks Again for taking a look.
I checked the sysprep log in the image and they look fine. No errors.
As requested here are some logs. Let me know if I can provide anything else.
BDD.log
litetouch.log
SMSTS.log
Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine. -
2 Apple TVs. The first won't reboot, it stalled during an update and now shows a picture of a UBS plug. Ive tried to plug into my computer, nothing happens. At a standtill.
The second Apple TV works but only if I send something via Airplay. The remote no longer has any affect. The light on the front of the Apple TV blinks when I push a buttom on the remote but nothing happens.
Any Ideas? I am starting to think I need to replace them. Thanks.Ok, with itunes open on the pc, plug one end of the usb cord into the computer, but not connected to the ipad.
now, press the power button on the ipad until it turns off.
Then, press and hold the home button on the ipad at the same you plug the usb cord into the ipad. DON'T LET GO OF THE HOME BUTTON.
Keep holding the home button until you see the recovery mode message pop on the itunes window.
When that happens, you should now be able to restore. -
MDT 2013 Boot straight to CMD after upgrade?
Hi,
I've recently upgraded MDT 2012 to MDT 2013. My images are working if no changes are touched. However, right after I add NIC and other drivers for a new dell model ( e5550) and regenerate the image, all my models boot straight into CMD after the image gets
picked up via WDS. Very weird.
I have a snapshot of my deployment server just after the mdt migration so i can always fall back to the original state for my current models, but I need to resolve this to able to add new drivers and new models going forward.
I'm thinking it had something to do with installing windows 8.1 ADK and perhaps it changed the win PE version? I am new to MDT so there must be something obvious I am overlooking. Has anybody seen this before?
also, when would I be extracting the Dell WinPE cab to the boot image? And how I know which version to use?This is the set-up for my MDT. I dont have a seperate WinPE folder. is this best pratice or now required?
http://imgur.com/Bs2TnmL
Maybe you are looking for
-
For BSID- Accounting Document Number corresponding PO Number is required
Hi Gurus, I have got a requirement to develop a report similiar to 'FBL5N' . I am getting the details of open and cleared items of a customer from BSID and BSAD tables respectively. My requirement is also to fetch the corresponding PO nu
-
How to open new form and exit from the calling form on dual/multi language?
using form 10g 10.1.2.0.2. i have dual language application 1 english & 1 arabic and i created forms identically each respectedly to call and switch every forms when user choose any language it uses. say im in currently in english. how we can call th
-
Calling stored proc through JDBC
Hello all, What I am doing is calling a stored proceedure in this manner... CallableStatement stmt = dbB.getConn().prepareCall ("call LDPKG.LDGetData(?, ?)"); //dbB is a conn Class I made, it works fine and getConn obviously jsut returns teh Connect
-
Can't save "Play music during slideshow" setting in iPhoto 6
Hi, I just bought and installed iPhoto 6 today as an upgrade to iPhoto 4. I've discovered that I'm unable to save the "Play music during slideshow" setting in the dialog which appears when I click the "Play" button from the thumbnail screen to play a
-
Hello, i'm running a very complex system with multi-language (Java, C++, and Ada 95) applications communicating via a tnameserv running on an IBM server. When we were running the 1.3 version of the tnameserv we were seeing minimal problems, however,