Search results by user ID 3945

Re: SBS Exchange issue

it4offices — Mon, 03 Oct 2011 07:42:40 GMT

Hi Allan

the AD will be prepared, the issue is a time out of the replication. I suggest checking the obvious first.... network settings & time on both servers. The bugs in the install have been ironed out in the sbs 2010 but this probably does not help you at the moment.

You can try starting a command prompt during the pause - the task manager should allow you to do this. Then at least you can see if its network or time issues.

regards

Matt

Re: Migration issues

it4offices — Sat, 05 Feb 2011 18:18:08 GMT

Hi David

Thanks for the reply, exchange and AD seem to be ok, the main issue looks like the migration connect to internet wizards, although I can get past this using the fix my network wizard.

Can I uninstall exchange and demote the server from AD and restart the migration - is that the best way? there is a backup but the client is using email on the old server while I check the server. they need the server during the week so downtime is limited to friday nights and saturdays.

I've heard sbs 2011 is supposed to be easier to migrate than sbs2008 whats your view on this?

regards

Matt

Migration issues

it4offices — Sat, 05 Feb 2011 09:04:40 GMT

I'm trying to migrate a clients sbs2003 to sbs2008 and after logging into the sbs 2008 box it reports the installation failed.

However, AD is replicating as well as Exchange in installed, Sharepoint is installed but does not work. I've tried running some wisards, move data worked for everything apart from sharepoint data, when I run the internet setup task it reports it cannot configure and to run the repair wizards.

Can I reinstall the wizards and sharepoint? or does it mean a rebuild? I'm running a virtual sbs2003 as the client is using the same hardware for the 2008 box. So can I remove installed exchange/ad parts rather than restoring from tape? (which is out of action as its attached the 2008 box)

Truncated log below...

[3444] 110204.190641.9922: Task: ClientDeployment.GPOTask succeed with C:\Program Files\Windows Small Business Server\Bin\GPOTask.exe /config:C:\Users\administrator.REDINC\AppData\Local\Temp\tmp63CA.tmp
[3444] 110204.190642.0078: Setup: DoWork is trying function=Void OpenDSGPO() times=0
[3444] 110204.190642.0858: Setup: SetPolicy SOFTWARE\Microsoft\SmallBusinessServer\ClientSetup Version <6.0.5601> String 2
[3444] 110204.190642.0858: Setup: DoWork is trying function=Void SetPolicy() times=0
[3444] 110204.190642.2730: Task: Policy setting Software\Policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit:REDINC\Domain Admins:REG_SZ:REDINC\Domain Admins
[3444] 110204.190642.2730: Setup: SetPolicy Software\Policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit REDINC\Domain Admins <REDINC\Domain Admins> String 2
[3444] 110204.190642.2730: Setup: DoWork is trying function=Void SetPolicy() times=0
[3444] 110204.190642.8970: Task: Finish of task ClientDeployment.GPOTask
[3444] 110204.190642.8970: Task: In Task ConfigureGP:
[3444] 110204.190642.8970: Setup: Task ConfigureGP succeeded.
[3444] 110204.190642.8970: Task: Task ("ConfigureGP") execution complete.
[3444] 110204.190642.8970: TaskManagement: Exiting ProgressManager.UpdateProgress(100), not updating since the task is complete.
[3444] 110204.190642.9438: Task: Running Task("ConfigureSharePointTask") with TaskProcessor("NET").
[3444] 110204.190643.0062: Task: Getting the server name used during staging.
[3444] 110204.190643.0062: Task: The sharepoint url for the default site is: http://win-eugso7lo7py/
[3444] 110204.190643.0062: Task: Getting the port for SharePoint to listen on
[3444] 110204.190643.0062: Task: The port for SharePoint to listen on is: 987
[3444] 110204.190643.0062: Task: Building the Uri for the SharePoint site.
[3444] 110204.190643.0062: Task: The sharepoint url for the new site is: https://sites:987/
[3444] 110204.190643.0062: Task: Creating and provisioning the new sharepoint web application
[3444] 110204.191428.7130: Task: Getting an instance of DataLink.RuntimeData
[3444] 110204.191428.7130: Task: Adding the root sharepoint site to the web application
[3444] 110204.191428.7130: Task: The id for the template to use is: STS#0
[3444] 110204.191428.7130: Task: Currently logged on user: administrator
[3444] 110204.191428.7130: Task: Configuring SharePoint in DomainJoin scenario. Obtaining properties for currently logged on user
[3444] 110204.191458.8366: Task: Unprovisioning the default Wss V3 site: SharePoint - 80
[3444] 110204.191500.8958: Task: Setting the Default Website to AutoStart
[3444] 110204.191501.0674: Task: In Task ConfigureSharePointTask: Windows SharePoint Services is not configured.
[3444] 110204.191501.0674: Setup: Task ConfigureSharePointTask failed.
[3444] 110204.191501.0674: TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureSharePointTask" Task or the "NET" TaskProcessor threw an Exception during the ITaskProcessor.Run() call:System.Runtime.InteropServices.COMException (0x800705B4): This operation returned because the timeout period expired.

[3444] 110204.191501.0674: Setup: An error was encountered on the TME thread: System.Runtime.InteropServices.COMException (0x800705B4): This operation returned because the timeout period expired.

   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_AdsObject()
   at System.DirectoryServices.PropertyValueCollection.PopulateList()
   at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
   at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.get_DomainName()
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.QueryAD(DirectoryEntry root, String filter, String parameter, String[] attributes)
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.FindUserSearchResult(DirectoryEntry root, String userLogonName)
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.FindUser(String userLogonName)
   at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointTask.SetUserInfo(ITaskDataLink DataLink, String userLogin, String& userName, String& userEmail)
   at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointTask.Run(ITaskDataLink DataLink)
   at Microsoft.WindowsServerSolutions.TaskManagement.TaskProcessors.NetTaskProcessor.Run(Task currentTask, ITaskDataLink dataLink)
   at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink, IDictionary`2 taskProcessorMap)
   at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName)
   at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter._RunTasks(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter.TasksCompleted(Object sender, RunWorkerCompletedEventArgs e)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.WindowsServerSolutions.Common.Wizards.Framework.WizardFrameView.Create()
   at Microsoft.WindowsServerSolutions.Common.Wizards.Framework.WizardChainEngine.Launch()
   at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass._LaunchWizard()
   at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass.RealMain(String[] args)
   at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass.Main(String[] args)
[3088] 110204.191501.1922: Setup: Removed the password.
[3088] 110204.191501.2078: Setup: Deleting scheduled task at path Microsoft\Windows\Windows Small Business Server 2008 with name Setup
[3088] 110204.191501.7382: Setup: Removed SBSSetup from the RunOnce.

thanks in advance

Matt

Re: Clean installation I think?

it4offices — Wed, 10 Mar 2010 07:54:07 GMT

If you have the large amount of groups, it can be quiet a pain to change each one so they appear in the sbs mannager, so a cleaner install sounds like the better option for you.

I dont think the ADMT tool works any more for 2008 but a free tool which I've used in the past for users and pcs is ForensiT Domain Migration tool, it had a few issues - ie only being able to run it once on any one pc but I was using it on 2000 pro boxes into a sbs 2008 domain.

http://www.forensit.com/domain-migration.html

It allows quick migrations but you dont have a chance to rename the pcs. This can be done either before or after with only one restart I think.

Re: Outlook 2007 prompts for username after migration

it4offices — Tue, 09 Mar 2010 22:24:38 GMT

Hi David

After thinking the issue was resolved a few months ago - I noticed all users using outlook 2007 were getting the same issues again - this occurred at several different clients sites (even clean sbs 2008 builds)

Apparently, this is a known issue now - applying exchange 2007 rollup 9 or exhange 2007 sp2 using the sbs 2008 tool, resolves this issue.

Hope this helps other readers.

Matt

Re: Clean installation I think?

it4offices — Tue, 09 Mar 2010 22:12:00 GMT

Hi Zinny

If you have a large number of client pcs then migration of each of them over manually is very time consuming, the migration process for sbs 2008 can be tricky, I've completed 2 migrations and both had issues - which David and his book helped a great deal. A clean install of sbs 2008 worked very well for other clients.

In regards to your terminal server I think if you treated this as a number of client pcs, the migration is really your easier route. If your migrating, the terminal server should generally be unaffected until you change any group policies. Have you thought trying a virtual test environment, this will help you test if the processes will work for you.

good luck

Matt

Re: Outlook 2007 prompts for username after migration

it4offices — Wed, 23 Dec 2009 20:47:24 GMT

Yes - When the server was installing initially I was unable to move mailboxes between servers initially - obviously there must have been a break that caused this corruption. Even after it was re-established (by grabbing FSMO roles) the corruption remained.

Everything is working now so I can demote the server and finally shutdown the old sbs 2003 server.

Re: SBS Faxing Wizard issues

it4offices — Wed, 23 Dec 2009 20:43:19 GMT

After importing the GPO's from http://blogs.technet.com/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx

The fax wizard ran successfully.

Thanks

Matt

Re: SBS Faxing Wizard issues

it4offices — Wed, 23 Dec 2009 19:17:05 GMT

The Errors I had with this server were:

ConfigureExchangeEAPListTask: The Exchange E-mail address policy cannot be configured.

ConfigureGP: Windows Small Business Server group policies cannot be configured.
MUPhase2Task: One or more updates cannot be installed.
WSUSConfig: Windows Server Update Services cannot be configured.
ReDirOUTask:
ConfigureWSSOutgoingEmailTask: Incoming and outgoing e-mail for Windows SharePoint Services are not configured.
ConfigureWSSIncomingEmailTask: Incoming and outgoing e-mail for Windows SharePoint Services are not configured.

I'm working through recreating the group policies from:

http://blogs.technet.com/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx

And I've cross referenced the GUIDs etc

I'll keep posting the results as I get them.

Re: Outlook 2007 prompts for username after migration

it4offices — Wed, 23 Dec 2009 19:11:50 GMT

HI David

This server only had one issue - the dns sync

Matt