A client needs to have .NET Framework 4 installed and not patched so their software running on their Windows 2008 R2 Server functions properly.
This sparks the questions:
Perhaps this question should be in SE: Information Security?
If I were to create a admin domain account on a remote Windows Small Business Server (SBS), copy all permissions from the current [default] Administrator account, and then disable the [default] administrator account, then
How can I unlock the newer admin account if it gets locked out (besides a full system restore from a BDR)?
There will be no other admin accounts active on the server, but there will be standard user accounts.
The title is self explanatory. I had to remove the /generalize option when going from my sysprep to OOBE but that has now broken my copy profile.
I have read multiple places, that /generalize is needed for the copy profile and I cannot do this manually as the button to copy profile (in audit mode) is grayed out [to copy the profile ]..
Can I still perform the without the /Generalize when changing from my audit to OOBE?
If I need to script this - its okay.
I have a GhostCast server running for deploying images. I would like to have each ghost cast session to write to a file ( can be multiple text files or append to one file already there ) statistics. I know this is possible based on the options GhostCast software provides for writing to a log file, but I would like this automated for every image being backed up and restored. I don't want to have my employees click write to a new file every time.
Is this possible?
I am currently working on .xmls for imaging on mass deployment. I want to do an unattended join to the domain and also get the drivers in the audit (sysprep) phase. But when I go from audit to OOBE, I do a /generalize to cleanup the drivers I pushed down. [makes overall process a little faster, and the image smaller]
If I do the /generalize command from audit to OOBE, will that remove my [unattended] join to the domain?
I am looking to implement (if possible/feasible) the ability to image a PC and Mac via our wireless network. Is this actually possible? I have read multiple documents that newer Macbook Airs can do this, but would that require having Multicasting on within our entire network? We have only have it on in 1 VLAN to minimize chatter on our network. Right now we have a PXE boot to gain access to a ghostcasting session that we instantiate. Is it possible to setup a wireless (netboot?) to PXEboot to ghostcasting?
I figure sending that much data over our wireless network ( which serves 13k+ users) would use a good portion of available bandwidth per VLAN. ( about 50GB in our image )
Any Ideas / alternatives?
I have configured a Windows 2008 R2 Server for many users to connect to - but right now I have them all logging in with one account which is bound to our domain. The purpose of this server is for imaging other computers with a Ghostcast session. A user would login with the generic administrator account, create the session, then terminate the remote session. Seeing as that user terminated the remote session - not logged out - the ghostcasting would continue. If I had independent logins for every user connecting to my server, the server will log out the 3rd last user who logged in.
(Example: I log in with my individual admin account, create a ghostcast session and terminate the remote session. User2 logs in with their individual account, creates a ghostcast session and terminates the remote session. Once User3 logs in with their individual admin account, I get logged out completely and my ghostcast session is terminated.) (OR if three users happen to remote into the server at the same time with the same generic account, one user will be denied /logged out)
My question is, How can I have the ability for multiple user logins without logging the 3rd person out or is there a setting in the server I have missed?
I understand - depending on how many users there are - this will use up a considerable amount of server memory keeping many users logged in at the same time.
It would be better if I could have the ability for multiple users to remote in at the same time, rather than using a generic account so I can micromanage folder permissions.
I heard through the grapevine that WINS was going to be phased out / not supported officially from Microsoft any more [ and yet they have it in Windows server 2008 ]. I can't find any information about this on the web. Does anyone know of this rumor and/or have an official release from Mircosoft (URL?)? ( This question relates to Policy - large corporate networks)