Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.
Solved
local & domain path query
Posted on 2013-12-31
hi I am running a win 2003 domain and getting ready to migrate across to win 2008.
I have noticed something unusual and wanted to know if anyone can provide any advice.
step 1
usually I install win 2003 on the physical server and join as a member server to the domain. when I then open up the cmd prompt it shows the following path:
c:\documents and settings\administrator.dom
if I logon to this same member server (locally) and open the cmd prompt it shows the following as expected:
c:\documents and settings\administrator>
step 2
I have installed from a win 2003 cd the image onto my ris member server.
I then logged onto my (aduc) and pre-staged my isa 2006 firewall by adding the name: isa-20061a & the mac address successfully.
I then rebooted my other server and selected (f12) and installed win 2003 image successfully.
on completion of install I logged on as the domain administrator as it does not currently have a (local account) like (step 1) above as expected. I then opened up the cmd prompt:
c:\documents and settings\administrator>
I then created a new (local account) and opened up the command prompt and saw:
c:\documents and settings\administrator.isa
question 1. why is (step 1 different from step 2) ?
I have noticed something unusual and wanted to know if anyone can provide any advice.
step 1
usually I install win 2003 on the physical server and join as a member server to the domain. when I then open up the cmd prompt it shows the following path:
c:\documents and settings\administrator.dom
if I logon to this same member server (locally) and open the cmd prompt it shows the following as expected:
c:\documents and settings\administrator>
step 2
I have installed from a win 2003 cd the image onto my ris member server.
I then logged onto my (aduc) and pre-staged my isa 2006 firewall by adding the name: isa-20061a & the mac address successfully.
I then rebooted my other server and selected (f12) and installed win 2003 image successfully.
on completion of install I logged on as the domain administrator as it does not currently have a (local account) like (step 1) above as expected. I then opened up the cmd prompt:
c:\documents and settings\administrator>
I then created a new (local account) and opened up the command prompt and saw:
c:\documents and settings\administrator.isa
question 1. why is (step 1 different from step 2) ?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
3
7 Comments
Active today
That is completely normal and expected. Windows will always attempt to use just the account name when creating a profile directory. If it detects that the directory name already exists, then it appends the domain name for domain accounts or the machine name for local accounts to avoid the conflict. And if THAT already exists, it will start appending numbers counting upwards.
So which appended name you see will depend on which account got just the "administrator" directory first... domain or local.... and then the conflict resolution above kicks in.
So which appended name you see will depend on which account got just the "administrator" directory first... domain or local.... and then the conflict resolution above kicks in.
hi cgaliher,
important note:
what I forgot to mention before you read the below issue, originally I installed upto 99% of the updates sent from my wsus and did not have this issue below, but since completing a 2nd clean ris image install, I have not installed updates upto 99%. I just assumed because sp2 was installed I would not have this problem below now, but I do as below now shows.
the reason for installing all updates upto 99% locally was because the wsus server detects my member server but as soon as I install isa 2006 it no longer detects this isa server via my wsus server, even though updates are passed across, but I only realise this when I physically logon to my isa server and see that some updates are ready to install, except for those that install automatically that do not require a 'restart' due to my 'gpo settings'.
my isa has however detected via logging on locally '8 updates' so I am installing them now as my wsus has not pushed any updates down yet via the domain logon as clearly there has not been enough time for everything to sync up.
--------------------------
thanks for those comments. I have always installed 'win 2003' directly on the pc and not via a 'ris flat image'.
I have attached some screenshots of the messages I get.
step 1.
I logged onto the domain and attempted to install 'sp2' but I received a message about not having the rights.
resolution - I logged on locally and installed sp2 successfully
step 2.
I attempted to install 'isa 2006' but it stated: 'the system administrator has set policies to prevent this installation.
question 1.
resolution fail - I logged back onto my master dc selected: ou - for isa 2006 & right clicked 'properties' & selected 'members of' tab and added: domain admin & the delegation tab & selected: 'trust this computer for delegation to any service (Kerberos only) - but I still receive the same error - why ?
question 2. what I do not understand is if I copied the win 2003 image onto my 'ris domain member serverr' successfully and rebooted the other server which allowed me to select the 'win 2003 image' and logon with 'domain admin' account, then why do I now not have permission as an administrator ?
note: when I check the 'eventviewer' it states:
security - unable to complete the operation on 'security'. access denied
sp2---isa-2006-dont-have-permiss.docx
important note:
what I forgot to mention before you read the below issue, originally I installed upto 99% of the updates sent from my wsus and did not have this issue below, but since completing a 2nd clean ris image install, I have not installed updates upto 99%. I just assumed because sp2 was installed I would not have this problem below now, but I do as below now shows.
the reason for installing all updates upto 99% locally was because the wsus server detects my member server but as soon as I install isa 2006 it no longer detects this isa server via my wsus server, even though updates are passed across, but I only realise this when I physically logon to my isa server and see that some updates are ready to install, except for those that install automatically that do not require a 'restart' due to my 'gpo settings'.
my isa has however detected via logging on locally '8 updates' so I am installing them now as my wsus has not pushed any updates down yet via the domain logon as clearly there has not been enough time for everything to sync up.
--------------------------
thanks for those comments. I have always installed 'win 2003' directly on the pc and not via a 'ris flat image'.
I have attached some screenshots of the messages I get.
step 1.
I logged onto the domain and attempted to install 'sp2' but I received a message about not having the rights.
resolution - I logged on locally and installed sp2 successfully
step 2.
I attempted to install 'isa 2006' but it stated: 'the system administrator has set policies to prevent this installation.
question 1.
resolution fail - I logged back onto my master dc selected: ou - for isa 2006 & right clicked 'properties' & selected 'members of' tab and added: domain admin & the delegation tab & selected: 'trust this computer for delegation to any service (Kerberos only) - but I still receive the same error - why ?
question 2. what I do not understand is if I copied the win 2003 image onto my 'ris domain member serverr' successfully and rebooted the other server which allowed me to select the 'win 2003 image' and logon with 'domain admin' account, then why do I now not have permission as an administrator ?
note: when I check the 'eventviewer' it states:
security - unable to complete the operation on 'security'. access denied
sp2---isa-2006-dont-have-permiss.docx
Active today
To effectively use RIS, you need to generalize the image. When you don't do that, security permissions get smashed during the deployment. This restriction is true for WDS and MDT as well.
hi, I have never had this problem before as I normally install win 2003 os, on the physical machine.
yes if I was to use 'sysprep' then I remember seeing 'generalize', but I did not use that as it was not need hence only been using: riprep.exe as my machines are all identical.
im assuming 'delegation' enabling 'batch job or service or add machines to network' are not the answers then.
yes if I was to use 'sysprep' then I remember seeing 'generalize', but I did not use that as it was not need hence only been using: riprep.exe as my machines are all identical.
im assuming 'delegation' enabling 'batch job or service or add machines to network' are not the answers then.
Active today
Generalizing isnt just about hardware. It also properly scrubs SIDs, otherwise you get conflicts in the domain which absolutely breaks delegation.
we seem to be gong farther and farther from your originally posted question though. You asked why the two scenarios creates two different folder structures. that has been addressed and would NOT create permissions issues like you describe. So what you are describing now is unrelated to your initial question. Even at that, I have tried to assist you with information on the "right" way to fix your issue. The workarounds you suggest would not work. But I don't want to play whack-a-mole and get new twists with every update. So, with that, I will simply wish you luck.
we seem to be gong farther and farther from your originally posted question though. You asked why the two scenarios creates two different folder structures. that has been addressed and would NOT create permissions issues like you describe. So what you are describing now is unrelated to your initial question. Even at that, I have tried to assist you with information on the "right" way to fix your issue. The workarounds you suggest would not work. But I don't want to play whack-a-mole and get new twists with every update. So, with that, I will simply wish you luck.
hi, my original question yes you did answer my question, but due to installing 'isa firewall' and receiving the following message:
"the system administrator has set policies to prevent this installation"
I just assumed it was something to do with my main thread hence asking that last secondary question.
yes i have read about 'sysprep' which is for 3rd party software which i am not currently using.
ok i will close thread and appreciated for the main thread advice.
"the system administrator has set policies to prevent this installation"
I just assumed it was something to do with my main thread hence asking that last secondary question.
yes i have read about 'sysprep' which is for 3rd party software which i am not currently using.
ok i will close thread and appreciated for the main thread advice.
Featured Post
Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP, Windows Server…
- Ransomware
- Experts Exchange
- Windows XP
- Windows OS
- Windows Server 2008
- Windows Server 2003, Security
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers.
Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This Micro Tutorial hows how you can integrate Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease.
The following video show how to bind OSX Mavericks to …
Suggested Courses
Course of the Month8 days, 6 hours left to enroll
715 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.