kent
New Member
Posts: 2
|
Post by kent on Jan 8, 2019 7:35:03 GMT
An option to acknowledge that the computer exist in AD, but overwrite it. An error message with "A computer with this name already exists in in active directory, are you sure you want to use this name?" if you have set ADValidate="Warn" or somthing like that. |
|
|
|
Post by Jason on Jan 16, 2019 1:54:20 GMT
An excellent suggestion. Adding it to my backlog now.
I'm not sure if prompting the user is the right thing to do though. Would just a warning message be sufficient?
|
|
kent
New Member
Posts: 2
|
Post by kent on Jan 16, 2019 14:30:07 GMT
Yep, an warning is enough.
|
|
|
|
Post by Spinat on Feb 22, 2019 10:00:21 GMT
This is exactly what i too was looking for.
Would it be possible to make the AD authentication run with a fx. a predefined serviceaccount, skipping the prompt to the user?
|
|
levi
Junior Member
Posts: 57 
|
Post by levi on Feb 22, 2019 16:20:06 GMT
I would like to see this as well, with the option to use the USerauth credentials, or the cached OSD Domain Join/NAA accounts. I would like the option to prompt to warn, "Are you sure you want to overwrite {computername}"? I just imaged a VM and accidentally gave it the same name as our desktop. OOPS.
|
|
|
|
Post by Jason on Feb 26, 2019 22:44:40 GMT
Noted and in my backlog.
|
|
syv
New Member
Posts: 8
|
Post by syv on Mar 21, 2019 10:08:10 GMT
If you're on it, maybe you can add the option to customize the Error/Warning text? I know for a fact that some people will complain about my current work, even if almost everything is translated  |
|
|
|
Post by happysccm on Mar 31, 2020 4:03:30 GMT
Would love the warning option
|
|
|
|
Post by Jason on Mar 31, 2020 15:01:15 GMT
Working on it. It's in my current sprint which I've finally started after a year of being swamped with other priorities.
|
|
