Sysprep & Autologin issue

I'm hopping someone can spot my error, I've been looking at it way too
long. The problem is After sysprep the auto login doesnt work. It
brings up the Novell GUI as "Workstation only" with the Administrator name
populated but requires me to hit the enter key to log in and complete
sysprep. If I put ing the following changes but don not run sysprep the
machine will automatically login ok. I don't get it. Can anyone see the
flaw here? I am using the 3.91 sp3 client without NICI or NMAS (doesnt
seem to matter if I install them or not). I have tried the sp2 sysprep
and a previous version, no change.
Thanks any help will be appreciated.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultDomainName"=
"DefaultUserName"="Administrator"
"LegalNoticeCaption"=""
"LegalNoticeText"=""
"AutoAdminLogon"="1"
"AltDefaultUserName"="Administrator"
"AltDefaultDomainName"=
"DefaultPassword"=""
"DontDisplayLastUserName"="0"
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Login]
"NMAS Authentication"=dword:00000000
"Location"=dword:00000000
"Enable SSO"=dword:00000000
"AutoAdminLogon"="1"
"DefaultPassword"=""
"Show SSO"=dword:00000000
"Advanced"=dword:00000001
"Offline"=dword:00000000
"Local Login"=dword:00000001
"Default WS Only"=dword:00000001
"Variables"=dword:00000000
"AutoAdminQueryNDS"=dword:00000000
Remember WS Only"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Location Profiles\Services\{1E6CEEA1-
FB73-11CF-BD76-00001B27DA23}\Default\Tab3]
"DefaultUserName"="Administrator"
"DefaultDomainName" =
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\policies\syst
em]
"DisableCAD"=dword:00000000
"dontdisplaylastusername"=dword:00000000
"legalnoticecaption"=""
"legalnoticetext"=""
"shutdownwithoutlogon"=dword:00000001
"undockwithoutlogon"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZENworks\ZENWSR EG]
"ImportServer"=""
"LogLevel"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"System"=-
Sysprep command
%systemDrive%\sysprep\sysprep.exe -quiet -pnp -mini -activated -
forceshutdown -reseal

Blaine,
It appears that in the past few days you have not received a response to your posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at http://support.novell.com in both the "free product support" and "paid product support" drop down boxes.
- You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums)
If this is a reply to a duplicate posting, please ignore and accept our apologies and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

  • Sysprep + CopyProfile Issues

    Hello everyone, 
    I'm hoping someone can help me with this issue I've had trying to sysprep a Windows 8.1 image. I am using the 64bit Windows 8.1 Enterprise disc and did all the configuration through Audit mode. This is running inside VMware Workstation 10 with no fancy stuff
    turned on. I have built a new unattend file for Windows 8.1, validated it and there are no errors however when I boot up the image it fails on the specialize pass on the Windows Shell Setup component. The only settings I have set in this part of the unattend
    are CopyProfile True and a computer name. What is odd is the sysprep was successful the first time however I discovered a setting wasn't being applied properly (in the last pass of the unattend so its after specialize) so I reverted to a pre sysprep snapshot
    and tried to sysprep again and now it wont get pass the error I mentioned above. I'm at my wits end here. I should mention I have tried this on physical hardware as well and ran into the same error.

    Hi,
    One thing to note, and most people overlook this, is that the CopyProfile setting of the unattend.xml file is used during the deployment of Windows- NOT the unattend.xml file used to build the image.
    So as you normally would, create your Windows 8 image from your reference machine or VM, making all the customizations you need including, adding shortcuts to the desktop, remove provisioned apps, and re-organize the Windows 8 Start Screen, and finally sysprep
    and capture the image. Notice we didn’t make any changes to the unattend.xml file during the image build.
    Please also check "Troubleshooting CopyProfile" part of this article:
    Customize the Default User Profile by Using CopyProfile
    http://technet.microsoft.com/en-us/library/hh825135.aspx
    If the issue still persists, please upload your setup*.log Darrell mentioned for research.
    Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
    Kate Li
    TechNet Community Support

  • Win7 x64 SysPrep Image Issue

    I have been trying to create a new image that is syspreped for Windows 7 Pro x64. I have created the system and tried to take an image. I get about 75% into the image and the system seems to get stuck copying files up to the server. It run through the same set of files repeatedly without end. I let the process continue last night to see how long it would take before failure. I ended up stopping the process an hour and a half later. The system seemed to be processing the same group of files inside the Windows directory (something to do with amd64) for over a half an hour.
    I also tried to Multicast the image over to a different system (Master/Client) and the image became stuck at the same point.
    I did reboot and run the sysprepped system to see if something was wrong with the setup that would fail and give me an idea on what to fix. The sysprep ran and deployed as designed without error.
    Has anyone ran into this issue?
    System Specs: HP 6735b, Win7SP1x64 syspreped on a 50GigByte partition 3 Gig of RAM. (Only Windows no add-ons)
    ZCM > 10.3.1.0 / SLES10.2
    Thanks
    Rich

    I haven't tried this, but maybe you could ZIP the folder up so that later
    when you restore the OS image you restore the ZIP and extract. This would
    have to be done all from the imaging command line (bash).
    It's a really hacky way, but I think it could work.
    Jared Jennings
    Senior Systems Engineer, Computer Integrated Services (CIS)
    http://www.ciscony.com
    My Blog and Wiki with Tips, Tricks, and Tutorials
    http://jaredjennings.org
    Twitter@ jaredljennings

  • [SOLVED] LXDM Autologin Issue

    I am attempting to configure autologin for LXDE using LXDM by editing /etc/lxdm/lxdm.conf (autologin=username).  When I do so, I am logged into a session that looks unfamiliar.  It almost looks like a base openbox session or something with no wallpaper, no autostart scripts, etc.  If I manually choose LXDE from the session dropdown menu in LXDM, the proper session loads.  When choosing Default from the session dropdown menu in LXDM, I am logged into this unfamiliar session.  Anyone have any ideas on how to fix this?  Here is my /etc/lxdm/lxdm.conf file:
    [base]
    ## uncomment and set autologin username to enable autologin
    # autologin=
    ## uncomment and set timeout to enable timeout autologin,
    ## the value should >=5
    # timeout=10
    ## default session or desktop used when no systemwide config
    session=/usr/bin/startlxde
    ## uncomment and set to set numlock on your keyboard
    # numlock=0
    ## set this if you don't want to put xauth file at ~/.Xauthority
    # xauth_path=/tmp
    ## greeter used to welcome the user
    greeter=/usr/lib/lxdm/lxdm-greeter-gtk
    [server]
    ## arg used to start xserver, not fully function
    # arg=/usr/bin/X -background vt1
    [display]
    ## gtk theme used by greeter
    gtk_theme=Waldorf
    ## background of the greeter
    # bg=/usr/share/backgrounds/default.png
    ## if show bottom pane
    bottom_pane=1
    ## if show language select control
    # lang=1
    ## if show keyboard layout select control
    # keyboard=0
    ## the theme of greeter
    theme=Industrial
    [input]
    [userlist]
    ## if disable the user list control at greeter
    disable=0
    ## whitelist user
    white=
    ## blacklist user
    black=
    Last edited by Plus (2012-09-08 19:12:52)

    Terminator wrote:The configuration file is correct and LXDM should start LXDE by default, unless you override the default session in a file ~/.dmrc. If you have such a file, try renaming/removing it. If you don't, then I have no clue.
    It turns out Terminator was right.  I'm not sure where I was looking before but I do have a ~/.dmrc file and it was set to Session=openbox instead of Session=lxde.  I changed the setting and everything is working great now.  Thanks!

  • N100 Bluetooth Drivers and Sysprep issues

    Hello all,
    I'm using a 3000 N100 notebook running Windows XP Home Edition.
    After re-formatting and re-installing my OS using Rescue and Recovery, I have been experiencing 2 issues:
    1. Whenever Windows XP starts, I get the Sysprep Wizard and each option that I choose (It doesn't matter since I don't need to create more SIDs), The computer just shuts down/restarts and I'm not receiving any activation prompts (I don't even have the activation option on the system tools menu).
    2. When I try to access My Bluetooth Places (Start Using Bluetooth), I keep receiving an "Installing Bluetooth Drivers..." message that freezes and crashes the moment it comes up. I've tried uninstalling and re-installing the latest Bluetooth drivers from the website, but the problem presists.
    I thank you in advance for your assistance,
    Sharon

    Hello all,
    I'm using a 3000 N100 notebook running Windows XP Home Edition.
    After re-formatting and re-installing my OS using Rescue and Recovery, I have been experiencing 2 issues:
    1. Whenever Windows XP starts, I get the Sysprep Wizard and each option that I choose (It doesn't matter since I don't need to create more SIDs), The computer just shuts down/restarts and I'm not receiving any activation prompts (I don't even have the activation option on the system tools menu).
    2. When I try to access My Bluetooth Places (Start Using Bluetooth), I keep receiving an "Installing Bluetooth Drivers..." message that freezes and crashes the moment it comes up. I've tried uninstalling and re-installing the latest Bluetooth drivers from the website, but the problem presists.
    I thank you in advance for your assistance,
    Sharon

  • Issue restoring pre-sysprep image

    Hello,
    I'm having a bit on an issue with creating a pre-sysprepped base image with Windows 8.1. I've created my base installation, made all the changes and upload an image before I run the sysprep. Now when I restore this image after sysprepping to get back to all the changes I've made and edit it some more it boots into Windows fine but always creates a "dump"-user (Administrator.MACHINENAME) and not using the original Administrator account.
    Very irritating as I have to go back to my first install and re-do all my changes everytime I need to do a sysprep.
    Anyone know a way out of this?

    pastokes wrote:
    >
    > Hello,
    > I'm having a bit on an issue with creating a pre-sysprepped base image
    > with Windows 8.1. I've created my base installation, made all the
    > changes and upload an image before I run the sysprep. Now when I
    > restore this image after sysprepping to get back to all the changes
    > I've made and edit it some more it boots into Windows fine but always
    > creates a "dump"-user (Administrator.MACHINENAME) and not using the
    > original Administrator account.
    > Very irritating as I have to go back to my first install and re-do all
    > my changes everytime I need to do a sysprep.
    > Anyone know a way out of this?
    Do you run the machine on a VM? Do you run windows in audit mode?
    Niels
    I have always liked... Cowabunga!
    If you find this post helpful, please show your appreciation by
    clicking on the star below.
    A member must be logged in before s/he can assign reputation points.

  • Sysprep issues

    Hello everyone,
    We have purchased 6 X series ThinkPads. We ordered them with Windows Vista Business with the intention of downgrading to XP, in which I have successfully done on one of the laptops. I have the laptop all configured to our company needs. I then proceeded to sysprep the image using Zenworks. The image was successfully created but when I went to restore the image onto the second laptop all I get is a blinking cursor on the top left side of a black screen.
    Does anyone know of any known issues using sysprep after downgrading from Vista Business to XP.
    Thanks in advance.

    Hello everyone,
    We have purchased 6 X series ThinkPads. We ordered them with Windows Vista Business with the intention of downgrading to XP, in which I have successfully done on one of the laptops. I have the laptop all configured to our company needs. I then proceeded to sysprep the image using Zenworks. The image was successfully created but when I went to restore the image onto the second laptop all I get is a blinking cursor on the top left side of a black screen.
    Does anyone know of any known issues using sysprep after downgrading from Vista Business to XP.
    Thanks in advance.

  • Windows 7 Sysprepped Image - Injecting Drivers issue

    Hi
    I have created a Windows 7 Image, sysprepped it and capture an image using MDT. I am using the "Total Control" driver management method and during the imaging phase I can see that it injects the drivers into the image but for some strange reason,
    and I can't see to figure out why, it's not installing the drivers during the windows setup phase.
    Please can someone help!
    Thanks

    How do you know for sure the drivers are not getting installed, and how do you know for sure you have the correct drivers? Please illusrate. You should be able to boot into the new OS, open DevMgmt.msc, and update each missing device with drivers MDT copyied
    to the c:\Drivers folder, if these drivers don't install, then you might now have the correct drivers.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • A Sysprep question on SID changes

    Hello,
    I have an issue with Sysprep and the Generalize option in WIN 7.
    According to all M/S conventional wisdom I need to run this pass to remove COMPUTER NAME and SID's on a machine that I am going to deploy to the field multiple times.  I have created on the image a local user with restriction on desktop access
    via an LGPolicy.  Sort of like a Kiosk in a mall.
    When I run the GENERALIZE option, I lose the LGP restrictions on the local user because of the SID change.  Now I know after reading a metric-boatload of email and forum threads about being able to copy the .pol files and the USER/MACHINE folders
    to the new machine...  basically I've tried and it doesn't really work without alot of extra work after the fact.  Now I know stuff  like this can be scripted for automation... but I would like to shake the trees and get a response from the
    community to this thought...
    Why do I need to change the SID's on a machine that will NEVER connect to the network behind the firewall, only thru a VPN. All applications a client/server based and or Web based.  So there is no need to ID the machine or the user.  Since the
    user logs in via the VPN.  It is joined to the domain upon Imaging for any updates etc.. and registered in AD,  but after that it will NEVER touch the domain unless it is through a VPN. SO WHY RUN THE GENERALIZE PASS AT ALL?? Other than changing
    the computer name.. which I can do elsewhere. I dont need the SID change.
    This machine is used as a Mobile Data Terminal in a Public Safety environment, so I want to lock it down and have it autologin to a user upon powerup/reboot.  I do this to keep it simple for the officers to use.
    I have an Image that works, I just want to clone it to the field.
    any thought from the assembled masses??
    Warren Harris
    City of Dallas Mobile Technology Center

    Are you using Windows 7 Embedded or Enterprise?
    On a retail desktop OS, there shouldn't be any user accounts created at the time if you deploy your source OS to Audit Mode by default. I would then create a user group and assign policies to that group. Then when you sysprep the machine, the user account
    you create, specify the Group name you created (as opposed to Users or Administrators) and see if the changes still remain.
    Note that I have not actually set a local security policy in an image before. I just did a test where I disabled the UAC's Secure Desktop while in Audit Mode and did a sysprep/generalize and the setting was NOT lost. I tested on Windows 7 Ultimate SP1 x64.

  • Windows 8 Sysprep - Can't skip local account creation and autologon fails, wrong admin password.

    Using Windows 8 x64 Enterprise, Sysprep pauses to ask me to create a local user, which I don't want.
    If I enable SkipSystemOOBE and SkipUserOOBE in OOBE under Microsoft-Windows-Shell-Setup sysprep (in oobe mode) will skip user creation and autologon works.  But it only works correctly once.  If I run sysprep again, when it tries to autologon
    it will say that I have the wrong password for the local account.  After I type in the password manually it works.  If I use the same password for the local administrator account as for the autologon account, it looks to have the encrypted password
    twice with an equal sign after it.
    What I need to know:
    How to skip local user account creation (we run on a domain but I have it connect through scripts later)
    How to fix the autologon issue
    Do I need the local administrator account enabled for this to work?
    I have my unattend.xml file attached.
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <AutoLogon>
    <Password>
    <Value>[removed]</Value>
    <PlainText>false</PlainText>
    </Password>
    <Username>[removed]</Username>
    <LogonCount>2</LogonCount>
    <Enabled>true</Enabled>
    </AutoLogon>
    <FirstLogonCommands>
    <SynchronousCommand wcm:action="add">
    <Order>1</Order>
    <CommandLine>c:\folder\abatchfile.bat</CommandLine>
    <RequiresUserInput>false</RequiresUserInput>
    </SynchronousCommand>
    </FirstLogonCommands>
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    <NetworkLocation>Work</NetworkLocation>
    <HideLocalAccountScreen>true</HideLocalAccountScreen>
    <ProtectYourPC>3</ProtectYourPC>
    </OOBE>
    <TimeZone>Eastern Standard Time</TimeZone>
    <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
    <RegisteredOrganization>Company Name</RegisteredOrganization>
    <RegisteredOwner>CompanyName</RegisteredOwner>
    </component>
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <UserLocale>en-US</UserLocale>
    <UILanguage>en-US</UILanguage>
    <SystemLocale>en-US</SystemLocale>
    <InputLocale>en-US</InputLocale>
    </component>
    </settings>
    <settings pass="specialize">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ComputerName>*</ComputerName>
    </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:[removed]/sources/install.wim#Windows 8 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    The user accounts-creation page in Windows Welcome is suppressed if a user or a group is added to a local security group. Add a user or a group to a local security group by doing one of the following:
    Create a local user.
    Add a domain user to a local security group with the Microsoft-Windows-Shell-Setup | UserAccounts unattended installation setting.
    To suppress the user accounts-creation page in Windows Welcome, without creating a local user, use one of the following workarounds:
    Workaround 1
    If the computer is already joined to a domain, use the following XML example to add the Domain Users security group to the Local Users security group.
    <DomainAccounts>
     <DomainAccountList wcm:action="add">
      <DomainAccount wcm:action="add">
      <Group>Users</Group>
      <Name>Domain Users</Name>
      </DomainAccount>
      <Domain>FabrikamDomain</Domain>
      </DomainAccountList>
    </DomainAccounts>
    Because joining a domain automatically adds the Domain Users security group to the Local Users security group, the DomainAccounts command does not affect the membership of the Local Users group. However, using this XML example to join a domain will also suppress
    the user accounts-creation page in Windows Welcome.
    Workaround 2
    Use the Sysprep/Quit command to set the following registry value to 1:
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE\UnattendCreatedUser
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

  • Re-Imaging and Security Related Trust Issues

    Hello,
    Yesterday, I asked the question about how to fix having trust issues all the time when re-imaging computers in a school environment. I am using Windows Server 2008R2 and a Windows 7 Image created in FOG image program. The machines we use are HP5100 Desktop
    machines.  I didn't feel that I properly explained in the first post how we re-image the machines. I am hoping this will give you a better idea of what we are doing, and you can help me figure this issue out. Thank you in advance.
    Step 1: Bring Windows 7 Image down to an HP5100 Desktop, update plugins and send image update back up in Fog
    Step 2: Delete all machines out of the active directory for specified labs.
    Step 3: Re-image school labs of 30 machines each
    Step 4: Rename each machine with unique id, example : BJSHS203S01DW7 (name of school, lab #, Student #, and OS)
    Step 5: Join the domain
    Step 6: Make necessary adjustments, and use deep freeze to freeze machines up
    Those are the steps we use when re-imaging, and so far for the past two years we have sporadic issues with two labs in particular with receiving trust-relationship message, and also sometimes get a message that says there are no servers available. When this
    happens, then I need to go to the machine unfreeze it, unjoin the domain, delete the name from the active directory, and then rejoin the domain. Sometimes this works but more often than not it doesn't work so well, and then I have to go through the whole process
    again. We do not use sysprep on our machines.
    So my question is this : What am I doing wrong? Is there anything you can recommend to fix this problem so that I don't have to continue to fix the machines and waste time?
    Thank you in advance, I appreciate your help!!
    Angie

    Deep Freeze may be causing your problems.  Have you read this article from Deep Freeze makers about trust relationship issues?
    http://support.faronics.com/Knowledgebase/Article/View/365/8/computers-running-deep-freeze-loose-connection-to-or-fall-off-the-domain-with-an-error-that-the-trust-relationship-between-the-domain-controller-and-the-workstation-has-failed

  • Reboot before sysprep when I want to add an installation task with Office 2013

    Hi all,
    I want to buid a reference computer with a genuine Win7 wim file, correct drivers, uptodate patches, and usefull applications. So I use a “Build and Capture Task Sequence”. The new reference image captured, I can use it with WDS or a media
    to any computers, using a second and different “Build and Capture Task Sequence.”
    All things were right, I could add Acrobat Reader, Java and some others application, but it failed when I tried to add “Add Application Task” with Office 2013. I could import the software, I discovered the new panel to configure config.xml
    and mychoice.msp, but when I run the Tasq sequence, when it begin to sysprep the OS, a few time before the capture, the computer reboots. Sysprep does not run, and the image is not captured.
    I can add any software installation in the Tasq sequence but not one with Office 2013.
    What do you think about this issue?

    Hi,
    Some pieces of advice, since I have managed to create a Windows 7 WIM file with Office 2013 embedded without any problems:
    Build your reference image in a virtual machine, not on physical hardware, to prevent a gigantic driverstore with drivers for one or more models, and having to rebuild your image every single time you use a new model. This is not how MDT works, MDT works
    hardware agnostic, since it inject's drivers of hardware for each model before the WIM file is applied to your target computer.
    Do you really want to embed applications like Adobe Reader and Java in the image? They have a release every month. Do you want to (or is there room for) updating your image every single month? Put them in the deployment phase of your task sequence. This
    way these applications are left out the WIM file, but are installed after the WIM file is applied to your system. Yes this takes a little bit more time when deploying a machine, but that's time you'll save on not managing your WIM file every single month
    Check your
    log files, make sure your machine is not Domain Joined, since that is the biggest mistake people make when sysprepping a machine. And check
    Setuperr.log for any sysprep errors. Guaranteed it has noting to do with Office 2013
    Good luck!
    If this post is helpful please click "Mark for answer", thanks! Kind regards

  • Office 2013 apps showing templates error after Sysprepping Windows 7 with CopyProfile setting

    Here is my setup:
    I installed Windows 7 Professional.
    I entered Audit Mode (which automatically logged me in as the built-in Administrator user) and installed the entire Office 2013 Professional Plus suite.
    In Audit Mode, I opened Word 2013 to get through the "new user" prompts, such as the opening movie that plays in all Office 2013 programs. I did this to ensure that any new users who log into the computer would not need to sit through these "new
    user" prompts.  I also rearmed Office 2013.
    I ran Sysprep with the CopyProfile setting in the Unattend.xml file, with the /generalize switch, and the /oobe switch. The CopyProfile setting copies settings from the built-in Administrator account to any new user who logs into the system.
    Both Windows and Office were successfully activated using KMS.
    Everything seemed to work, but there is one problem: when any user -- all of which are standard users rather than administrator users -- logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates
    on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally have been listed:
    "Sorry, we had trouble getting the featured templates and can't show them right now."
    Below the error message is a link that reads “Work Offline.” If you click the “Work Offline” link, the error message disappears and the templates appear as they should.  However, the error message re-occurs when the application is closed and re-opened.
    If I login as the built-in Administrator account (i.e., the account I used to modify the default profile), this problem does not occur at all when using Office 2013 programs.
    Any ideas?

    "logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally
    have been listed:
    "Sorry, we had trouble getting the featured templates and can't show them right now." "
    Is there any chance to let you skip the Start page for Office application? I mean that try to open Office application (such Word)and go to File > Options > Untick the option "Show the Start screen when this application starts". Try to re-launch
    the application again to check if the error still pop-up. If yes, I'm afraid the default build-in template is corrupted somehow and we need to copy a healthy one from another computer or totally rename normal.dotm documents from %userprofile%\AppData\Roaming\Microsoft\template.
    Afte that, please check if the issue still persists.
    Here is another thread with the similar topic for your reference:
    http://social.technet.microsoft.com/Forums/ie/en-US/09a69d4c-9e5f-489d-ba7b-2af79ff83596/deploying-normaldotm-through-oct-doesnt-work-in-office-2013?forum=officesetupdeploy
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_install/can-not-sign-into-office-2013-version/b6951c25-2fb5-4fc1-a667-2327b9da2f7f
    Tony Chen
    TechNet Community Support

  • X61 - Can't get sysprep'ed image to boot on it.

    Scenario
    I am the senior desktop analyst in the offices of an international business travel company.
    We recently won the Lenovo account and the employee of our company that manages the account needs to use a Lenovo laptop exclusively so I was sent a brand new X61 to configure for the rep.
    X61 originally came with Vista preloaded but I slapped XP SP2 on it using the enclosed bootable Rescue CD and six XP recovery CDs.
    Since we already use a single working corporate image for the 6 different non-Lenovo hardware platforms we currently use, I want to deploy the same image to this user.
    I was the person that created the image from scratch and I see no problem with it actually working on the X61.
    To create an image for the laptop, one of our fastest desktops was imaged with our corporate master image and brought up normally as if the PC was being readied for deployment.
    Once everything had completed, the HD in the desktop had the proper Lenovo x61 drivers added to it and the SATA drivers added to the sysprep.inf file as well.
    After that it was sysprepped, shutdown and left lying in its original desktop ready to be cloned over to the drive in the X61 where it would be booted up for the first time after sysprep, in the X61.
    So I would still be able to keep the preload on the x61's original hard drive, I used a SATA laptop hard drive from one of our current non-Lenovo systems for the image transfer to the x61.
    Problem
    When I clone the sysprepped image from the desktop hard drive over to the laptop hard drive, it refuses to boot in the IBM.
    It just sits at the screen with a blinking cursor doing nothing.
    Troubleshooting so far
    I have put the corporate image on the x61's original hard drive [with the XP preload] by just replacing the original data partition and leaving the recovery partition alone = blinking cursor.
    I have cloned the whole source drive over to the Lenovo preload HD, removing the recovery partition completely = blinking cursor.
    I have installed XP from the original CD using a USB-floppy drive and the F6 key to add the SATA driver during startup.
    Once completely installed, I figured that it had a valid boot sector and I Ghosted over the sysprepped image without the IB switch and I still get the blinking cursor.
    I have researched on the Internet using Google and have found a couple of links that seem to indicate what the problem might be and have listed them below
    Predesktop Authentication
    This has nothing to do with the issue at hand as this option lies in the BIOS under Security,FingerPrint.
    Its BIOS description also states that this option decides whether fingerprint access is required to boot the laptop and this option has been in the disabled state even while the laptop was booting the Factory Preload.
    SATA set to Compatibility instead of AHCI
    This setting only affects how the OS sees the HD, not how the laptop sees it and I tried it anyway and it has no effect.
    If your XP image isnt properly sysprepped to handle the SATA drive using the proper driver, you will need to set it to Compatibility mode to get into Windows.
    As it stands, this is not an issue as I have edited the sysprep.inf to add the SATA driver reference for this laptop and if it ever boots the image, I expect it to never BSOD but thats if it ever boots which it hasnt so far.
    Ghosting using the IB switch
    I was SO sure that this would fix the issue but I get the same blinking cursor.
    Booting into DOS and using Ghost 8.3, I ran "ghost -ib" and selected the sysprepped desktop drive as the source and the laptop drive as the destination and it still leaves me at the blinking cursor when I try it in the laptop.
    Re-creating the MBR
    I have done this two different ways, one using Norton GDISK and one using a regular Windows 98 bootdisk.
    The Windows 98 bootdisk kept saying "No fixed disks present" so it never worked.
    Nortons GDISK didnt have any issues re-creating the MBR on the laptop or on the laptop HD plugged in the desktop but the drive still doesnt boot.
    Signature failure error
    I have heard about people having the same issue as me and getting this error but so far I have not received this error.
    As of now, I have restored the XP SP2 preload back on to the laptop to get the original boot sector back as I believe that is the key to solving this whole nightmare.
    There are other things I have tried as well and since I have been at it exclusively for almost two full business days now, everything is much upstairs right now but I will remember what I have tried if anyone wants to e-mail me any suggestions. 
    I await and welcome anyones advice.
    Solved!
    Go to Solution.

    Hi all,
    Sorry about not updating this thread but here is the solution and the explanation, hopefully, I dont miss anything because I would like this all in one place so it can be referenced in the future.
    The Lenovo's and the Dell's and maybe other OEM's [not Fujitsu-Siemens] use a recovery partition and the boot table that references it is based on some form of Linux as also is the recovery partition itself.
    As far as I know, all flavors of Linux use 8,192 bytes for a boot table [4 sectors of 2048 bytes each] whereas a standard boot table is only 1 sector and 2048 bytes long.
    This is the reason for the problem that happens with OEM laptops like this one.
    What you need to do to get the image to boot is the following [BSODs after booting is another issue]
    Create the image to a ghost file on whatever platform you want but use the IB switch in Ghost to create the image with the boot table intact.
    Deploy the image to the IBM laptop hard drive ALSO using the IB switch
    When doing ANY image deployment to the laptop, the hard drive MUST be IN the laptop itself. The laptop writes its boot sector differently so the hard drive must be in it for the image to work. I was doing everything right but this step and I was still having the issue so this is crucial.
    If you are testing the image by deploying straight from the test PC to the laptop by using the Ghost Peer-2-Peer TCP/IP option, start Ghost on both ends with the IB switch but remember the destination SATA drive MUST be in the laptop itself.
    Thats it.
    Hope this helps everyone out.

  • Remote Desktop Connection to VM does not work after sysprep

    Hello altogether.
    Often asked, but never answered with an applicable solution!
    What shall
    we
    do if
    we
    get no access to a Azure VM via Remote Desktop
    Connection?
    Everything went well: access to the VM via RDC was working perfectly!
    Then
    the idea came into
    our
    mind to create an image of the VM by use of the Azure Management Portal.
    We
    found that
    we
    had to apply “sysprep”
    on the VM.
    We
    did it.
    Then we did not take the image and decided to go on with the VM.
    But if we start the VM we get no access via RDC!
    We tried to find a solution by reviewing the already published contributions by other Azure
    users. But none of the replies marked as answered supply with a qualified solution.
    So can one provide a really applicable solution to us on how to arrange the further use of the VM?
    Thank you in advance.

    There is an issue right now where the VM may start unexpectedly after you have run sysprep and selected the shutdown option (which is normally what you should do).
    http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown?forum=WAVirtualMachinesforWindows
    But regardless of that issue - you can't use that deployed instance of the VM after you've run sysprep on it. It needs to stay shutdown, then you select Capture to create an image from it.
    If you start it back up, either intentionally, or it is started unexpectedly because of the issue above, it will be sitting at the first interactive screen of setup. RDP is not working at that point, and since there is no console access to an Azure VM, there
    is no way to get past that prompt.
    For other scenarios, you might be able to attach the OS disk of that VM as a data disk to another VM, and while you could do that in this case too, there is no supported method for disabling sysprep at that stage of setup.
    So while you could attach it to another VM to get data off of it (you would have to remove the VM first), the VHD is no longer in a supported state to use as a VM itself.
    Thanks,
    Craig

Maybe you are looking for