Windows 10 Enterprise v1703 is ignoring the computername is unattend.xml

February 1, 2018, 7:09 am

≫ Next: What is the release date for 2017.3 for on-premise customers?

≪ Previous: Query File Permissions

$

0

0

Hello everyone:

 

I have a fairly simple unattend file.  I use the %ldhostname% variable to allow dynamic naming during the imaging process.   I have checked and the injected unattend has the correct computer name.  However, when the computers boot, they will be named "Desktop-xxxx"   Has anyone experienced this?

 

Unattend file:

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

   <settings pass="auditSystem">

        <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">

 

            <UserAccounts>

                <LocalAccounts>

                    <LocalAccount wcm:action="add">

                        <Password>

                           <ValueRedacted</Value>

                            <PlainText>true</PlainText>

                        </Password>

                        <Description>Local Admin</Description>

                        <DisplayName>Redacted</DisplayName>

                        <Group>Redacted</Group>

                        <Name>Redacted</Name>

                    </LocalAccount>

                </LocalAccounts>

            </UserAccounts>

        </component>

    </settings>

    <settings pass="oobeSystem">

        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

            <OOBE>

                <HideEULAPage>true</HideEULAPage>

                <HideLocalAccountScreen>true</HideLocalAccountScreen>

                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>

                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>

                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>

                <NetworkLocation>Work</NetworkLocation>

                <SkipMachineOOBE>true</SkipMachineOOBE>

                <SkipUserOOBE>true</SkipUserOOBE>

                <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>

           </OOBE>

            <UserAccounts>

                <LocalAccounts>

                    <LocalAccount wcm:action="add">

                        <Password>

                            <Value>Redacted</Value>

                            <PlainText>false</PlainText>

                        </Password>

                        <Description>redacted</Description>

                        <DisplayName>redacted</DisplayName>

                        <Group>redacted</Group>

                        <Name>redacted</Name>

                    </LocalAccount>

                </LocalAccounts>

            </UserAccounts>

        </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">

            <InputLocale>en-us</InputLocale>

            <SystemLocale>en-us</SystemLocale>

            <UILanguage>en-us</UILanguage>

            <UserLocale>en-us</UserLocale>

        </component>

        <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">

            <OOBE>

                <HideEULAPage>true</HideEULAPage>

                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>

                <NetworkLocation>Work</NetworkLocation>

                <SkipMachineOOBE>true</SkipMachineOOBE>

                <SkipUserOOBE>true</SkipUserOOBE>

                <HideLocalAccountScreen>true</HideLocalAccountScreen>

            </OOBE>

            <AutoLogon>

                <Password>

                    <Value>redacted</Value>

                    <PlainText>false</PlainText>

                </Password>

                <Domain>.\</Domain>

                <Enabled>true</Enabled>

                <LogonCount>2</LogonCount>

                <Username>redacted</Username>

            </AutoLogon>

        </component>

    </settings>

    <settings pass="specialize">

        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="wow64" 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>%ldHostname%</ComputerName>

            <ProductKey>redacted</ProductKey>

        </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">

            <InputLocale>en-us</InputLocale>

            <SystemLocale>en-us</SystemLocale>

            <UILanguage>en-us</UILanguage>

            <UserLocale>en-us</UserLocale>

        </component>

        <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>%ldHostname%</ComputerName>

        </component>

    </settings>

    <cpi:offlineImage cpi:source="wim:redacted" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

---

What is the release date for 2017.3 for on-premise customers?

February 21, 2018, 6:10 am

≫ Next: Pre-Installation Provisionierung

≪ Previous: Windows 10 Enterprise v1703 is ignoring the computername is unattend.xml

$

0

0

What is the release date for 2017.3 for on-premise customers?

Pre-Installation Provisionierung

February 22, 2018, 4:21 am

≫ Next: Specific user data export from one site to another (different schemas)

≪ Previous: What is the release date for 2017.3 for on-premise customers?

$

0

0

Servus zusammen,

 

und gleich vorweg sorry für die vermutlich sehr grundlegende Frage:

 

Wie regelt ihr welche Software auf einem neu installiertem Rechner gleich beim Aufsetzten mit installiert wird?

 

Der IST Stand bei uns ist, dass man nach dem ersten PXE Boot den Rechner benennt und in eine OU schiebt worüber man das OS bestimmt welches dieser dann erhält.

Zusätzlich gibt es noch ein paar wenige Policies mit Nacharbeiten o.Ä. direkt auf der OU.

Alle weitere Software wie z.B. Office, Branchensoftware o.Ä. wird nachher über den Softwareshop zugewiesen (Durch den aufsetzenden Admin, nicht den User) - es ist also ein manueller Eingriff nötig auch wenn die Pakete selbst dann vollauto installieren

 

 

Gerne würde ich schon beim Aufsetzten festlegen welche Software der Rechner noch erhält, so dass ein praktisch kompletter Rechner nachher das Ergebnis ist.

Gibt es hier eine Möglichkeit z.B. über das PC Objekt zu parametrisieren ob der PC eine Office Policy erhalten soll?

 

Grüße

Lunex

Specific user data export from one site to another (different schemas)

February 22, 2018, 6:28 am

≫ Next: Which functions are available with the Viewer role in Xtraction 2018.0?

≪ Previous: Pre-Installation Provisionierung

$

0

0

We have our current production site which is at version 10.0 with a database schema of 10.0.5.  Our new data center is running the latest FR4 suite, with a database schema of 10.1.153.

 

We are moving a subset of users to our new site, so a database restore from 10.0 to FR4 will be fine, but as we add more users, I don't want to just keep restoring, basically wiping any changes from the users we initially moved to the new site.

 

I opened a support case asking this question and they had mentioned that I could use the EMPMigrate from the Environment Manager, but once I asked if I needed to use the EMPMigrate from the new site (FR4) as opposed to the old site (10.0) they basically stated that the databases have to be at the same version (schema).

 

Is this the case?  Are there any SQL scripts that would accomplish this task?  I know one option is to dump everything to native locations then use profile migration to get the data back in but we are moving users who are on non-persistent VDI first, so that option won't really be a feasible option.

Which functions are available with the Viewer role in Xtraction 2018.0?

February 15, 2018, 7:19 am

≫ Next: LDAP Settings Configuration Jumpcloud Error

≪ Previous: Specific user data export from one site to another (different schemas)

$

0

0

Hello,
Is it possible to  export of shared documents?

Is there a documentation about the user roles (Viewer, Designer, Private Designer) and functions?

Thanks in advance

LDAP Settings Configuration Jumpcloud Error

February 21, 2018, 6:19 am

≫ Next: Workflow process rate

≪ Previous: Which functions are available with the Viewer role in Xtraction 2018.0?

$

0

0

Hello everyone,   when we try to connect to the Cloud Directory Service "Jumpcloud" from one of our clients, we get the error message shown in picture 2. Something about the syntax seems to be off. Does any of you have a suggestions or experience with this?   We already implemented the certificate from the JumpCloud service on the server and openend the SSL port to access the Jumpcloud server.     (The distinguished name contains an invalid syntax)     When trying to leave the Base DN empty with following configurations we get two different error messages: (The LDAP-Server is not available)   Does any of you have advice for me and my colleagues? I also thought about the filtering which might be falsely defined. We are currently trying various alternatives.   Kind Regards, Vincent

Workflow process rate

December 18, 2017, 10:54 am

≫ Next: Filtering out Saturday and Sunday in Time to Resolve

≪ Previous: LDAP Settings Configuration Jumpcloud Error

$

0

0

Is there a way to increase the number of workflows processed by ISM?

I am dealing with a customer having so many workflows in the queue and looking to get them processed quicker.

 

Best regards,

 

Simone

Filtering out Saturday and Sunday in Time to Resolve

February 22, 2018, 7:19 am

≫ Next: Agentless scan configuration

≪ Previous: Workflow process rate

$

0

0

Hey Xtraction folks,

I've not spent a ton of time on this side of the house, but may start.

 

I need some help.  I've got a request to be able to filter out weekends from the "Time to Resolve (In Days)" field expression.  I know currently it just does a date difference between resolved and time opened, but I'm hoping someone can shed some light on doing this.  Or, better yet, if someone has successfully done so, helping a fellow community guy out. 

 

Thanks!

Jamie

---

Agentless scan configuration

February 22, 2018, 7:11 am

≫ Next: Änderungen der Kennwörter in der Konfiguration - Supervisor ist wo einzustellen?

≪ Previous: Filtering out Saturday and Sunday in Time to Resolve

$

0

0

Hello,

 

I am new to Ivanti products, so please excusse my shallow knowledge.

 

My goal is to make a network scan on a virtual network witch only virtual machines on it without any agents installed on the client PCs. On the Windows server I´ve got Ivanti Management Console installed. I´ve already made a scan of unmanaged devices, which showed all the devices in network.

 

But should I do, if I want to see more informations of all devices? I´ve tried the agentless scan on the subnet, but with no results. I´ve followed instruction on how to make an agentless scan.

 

Can you please give an advice what should I do?

 

Thank you for your help

Lukas

Änderungen der Kennwörter in der Konfiguration - Supervisor ist wo einzustellen?

February 22, 2018, 4:09 am

≫ Next: Use of Task/Template Instantiation Workflow Block

≪ Previous: Agentless scan configuration

$

0

0

Hallo in die Runde,

 

aktuelle Umgebung: 2016.1.3

 

Wir müssen in einer unserer Umgebungen die Passwörter ändern.

Ich habe bisher auch alle Nutzer in der Konfiguration gefunden.

 

Den den ich nicht finden konnte ist der Supervisor Nutzer.

 

An welcher Stelle wird dieser innerhalb der Konfiguration abgeändert?

 

VG
Tobias

Use of Task/Template Instantiation Workflow Block

February 22, 2018, 12:12 am

≫ Next: Windows Updates on Core

≪ Previous: Änderungen der Kennwörter in der Konfiguration - Supervisor ist wo einzustellen?

$

0

0

Hi all,

 

I would like to know what the Task/Template Instantiation workflow block does and how I can use it. I did check the admin help file but I did not get enough information and it doesn't provide examples on usage.

 

Has anyone already made use of this workflow block? If yes, could you kindly provide a scenario on how this workflow block was used?

 

Thanks in advance

Windows Updates on Core

February 21, 2018, 2:04 pm

≫ Next: Fehler im Advanced Patch Management

≪ Previous: Use of Task/Template Instantiation Workflow Block

$

0

0

2017.3

 

Hello what is the best practice for our core? Do we disable it? and if so, how do we apply security updates to it?

I say disabled because it happened to me that an update broke one of more cores.

We are runnign Server 2016  (https://social.technet.microsoft.com/Forums/lync/en-US/d3a2694c-32da-4158-943a-81c2904ffb3d/disable-automatic-updates-in… )

Any advice is appreciated.

Best.

Fehler im Advanced Patch Management

January 9, 2018, 12:58 am

≫ Next: Edit email notification template - but change not occuring

≪ Previous: Windows Updates on Core

$

0

0

Hallo in die Runde,

 

wir haben schon ein Ticket beim Support offen, bekommen dort jedoch schon länger keine Antwort mehr. Daher jetzt mal hier die Frage. Eventuell kennt jemand das Problem und hat eine Lösung.

 

Wir arbeiten mit der neusten DSM Version und haben diverse Geräte mit unterschiedlichen Windows Betriebssystemen, die über das Advanced Patch Management gepatcht werden. Vorrangig geht es um die Microsoft Patche. Es gibt etliche Systeme, die nicht mit DSM aufgesetzt wurden, sondern nur gemanaged werden.

 

Im vergangenen Jahr haben wir eine Patch Policy angelegt über die diverse Patche verteilt und auch erfolgreich installiert wurden. Im Zuge einer "Entwicklung" haben wir diese Policy Regeln und Kategorien später noch einmal neu aufgeteilt, anders angelegt und die alten gelöscht. Mit den neuen Policies werden nun aber die bereits installierten Updates nicht mehr erkannt und erscheinen permanent mit dem gelben Symbol im DSM. Weder erfolgt eine echte Installation noch eine korrekte Deinstallation. Diese gelben, "alten" Updates sind aber installiert und man kann sie auch auf den Systemen finden. Neue Updates werden ordnungsgemäß über die neue Policy installiert und werden dann auch grün.

 

Der Witz ist, dass in den Sicherheitslücken die gelben Updates als geschlossen deklariert sind. DSM erkennt also sehr wohl, dass die bereits installiert sind, gibt aber den Status nicht korrekt zurück. Das Symbol wird nicht grün.

Kennt irgendjemand das Phänomen und hat eine Idee, wie man den Fehler beheben kann? Es verwirrt sehr, wenn man fast nur gelbe Geräte hat und die Zeit alle Patche und Geräte auf Richtigkeit zu prüfen, fehlt einfach.

 

Ich hoffe, ich konnte das einigermaßen verständlich erklären. Wenn nicht, her mit den Fragen.

 

Viele Grüße und danke!

Edit email notification template - but change not occuring

February 22, 2018, 7:59 am

≫ Next: How do I update the greeting in IVR?

≪ Previous: Fehler im Advanced Patch Management

$

0

0

Edit the content of the notification emails.

 

 

Newbie question:  I suspect: a basic thing has not been done.

 

I am making text changes to the New Incident Notificationemail  template but the emails the system is  firing do not reflect the change I have made.

 

On the action “client receives email upon new incident” template I have changed a single word in the template.

 

I am updating the template in location:

Build -Automation Tools -Quick Actions -Business Object Incident#

 

I select the New Incident Notification and edit.

 

Make the change and then save.

 

Simply changed the word Logged to the word Created

 

I save it. The change appears however the actual emails the system is generating do not reflect this change. 

 

Is there some sort of commit action I am missing?

How do I update the greeting in IVR?

February 14, 2018, 8:54 am

≫ Next: MS18-02-W10_INTL causing multiple reboots

≪ Previous: Edit email notification template - but change not occuring

$

0

0

How do I update the greeting in IVR?

---

MS18-02-W10_INTL causing multiple reboots

February 22, 2018, 11:04 am

≫ Next: Verhalten der DSMC nach Update auf 2017

≪ Previous: How do I update the greeting in IVR?

$

0

0

Is anyone else having issues with the detection logic for this months Windows 10 patches?

 

I continue to get the same error on a couple machines: Registry key 'SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17', value 'CurrentState', contents '64' should contain '112'

 

The machine just continually attempts to patch, say's it was successful, asks for a reboot, but the detection doesn't go away.

 

I found this article: https://support.microsoft.com/en-us/help/4074588/windows-10-update-kb4074588

stating:

Even though the update was successfully installed, Windows Update incorrectly reports that the update failed to install. Select Check for Updates to confirm that there are no additional updates available.

You can also type About your PCin the search box on the taskbar to confirm that your device is using the expected OS build.

Microsoft is working on a resolution and will provide an update in an upcoming release.

Verhalten der DSMC nach Update auf 2017

February 20, 2018, 8:23 am

≫ Next: Calculation for DateTime Field from Incident to Problem

≪ Previous: MS18-02-W10_INTL causing multiple reboots

$

0

0

Hi @ all!

 

Seit dem Update auf 2017 fallen uns vermehrt - sagen wir mal unschöne - Verhaltensweisen der DSMC auf.

 

- Wenn man mehrere Policyinstanzen markiert fängt die DSMC erst mal ne Ewigkeit an zu laden. Je mehr Policies desto länger das Laden

- Wenn man in der Ansicht das Patchmanagement einblendet und etwas den Baum runter navigiert und markiert (z.B. Citrix -> Receiver)
und anschließend in der Softwarebibliothek die Patche durchsucht bleibt der Focus des Patchmanagements aktiv und man sieht z.B. nur die Patches des vorherigen auswahl (z.B. wie vorher Citrix Receiver)

- Nach lokaler Ausführung der Softwareinstallation (F7) gehen alle Supervisor-Rechte verloren und man muss die DSMC neu starten damit man überhaupt wieder damit arbeiten kann, sonnst kommt die Meldung

Warning (Module:esiConsoleExt, Severity:0x03): Error #-536598768:

Der angemeldete Benutzer darf die Aufgabe für das Object mit der ID 175 nicht ausführen, das Recht 'Lesen' (read) ist erforderlich.

The authenticated user is not authorized to perform this action on an object with ID 175, the right 'Read' (read) is required.

Sporadisch passiert das auch einfach mal so, mit F7 ist es zumindest bei uns reproduzierbar.

 

 

Kann das verhalten jemand bestätigen oder hat ggf. sogar einen Workaround?

Danke schon mal dafür :-)

Calculation for DateTime Field from Incident to Problem

February 22, 2018, 11:11 am

≫ Next: Problem with window calc firing on Yes/No attributes.

≪ Previous: Verhalten der DSMC nach Update auf 2017

$

0

0

In my Incident workflow, I have a 'Create Problem from Incident' action, and then an automatic action to create a problem, with certain fields being populated from attributes within the Incident.

Everything is working for the text fields using value types, but I am having some difficulty populating a DateTime from another DateTime.

 

This is my current calculation:

import System

static def GetAttributeValue(Problem):

     Value = Problem.IncidentProblems.Incident._INTimeOfRestoration

     return Value

 

That gives the error: "'Touchpaper.Framework.Data.DataObjectListProxy.Incident' not found"

But all my text values I am able to pull from the Problem.IncidentProblems.Incident collection.

Problem with window calc firing on Yes/No attributes.

February 22, 2018, 11:19 am

≫ Next: Reports coming back blank?

≪ Previous: Calculation for DateTime Field from Incident to Problem

$

0

0

I am working on a Request window and am trying to set a field to be mandatory should either of these Yes/No fields be set to "Yes". I have the Yes/No fields set to 'calculate on change = Yes' in the window manager and when I perform a test on the calculation against a request record that I know SHOULD work, it comes back true like it should. The issue is that on the request window itself the field is not being set to Mandatory until after I hit the save button rather than making it required at the time 'Yes' is selected. below is an attached image of the calculation and the test results.

 

Reports coming back blank?

February 22, 2018, 11:20 am

≫ Next: CBA not loaded - linked to Database?

≪ Previous: Problem with window calc firing on Yes/No attributes.

$

0

0

is anyone else seeing this? When we use the reports under reporting they don't work

 

Standard reports\Security\Vulnerabilities

 

they don't display any information when ran?

 

Also any good documentation on how to create your own.

 

for example detected Vulns in last N days returns a blank page.